Return-Path: X-Original-To: oracle-l@orafaq.com Delivered-To: oracle-l@orafaq.com Received: from puck1183.startdedicated.com (localhost [127.0.0.1]) by puck1183.startdedicated.com (Postfix) with ESMTP id 20A1619601B0 for ; Tue, 11 Nov 2014 20:08:37 +0100 (CET) Received: from turing.freelists.org (freelists-180.iquest.net [206.53.239.180]) by puck1183.startdedicated.com (Postfix) with ESMTP for ; Tue, 11 Nov 2014 20:08:37 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 60E8C33492; Tue, 11 Nov 2014 14:08:36 -0500 (EST) Authentication-Results: turing.freelists.org; dkim=fail (verification failed; insecure key) header.i=@gmail.com; dkim-adsp=none (insecure policy) X-Virus-Scanned: Debian amavisd-new at turing.freelists.org Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uR1zitnWl23g; Tue, 11 Nov 2014 14:08:36 -0500 (EST) Received: from turing.freelists.org (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 9D9B83347A; Tue, 11 Nov 2014 14:08:21 -0500 (EST) Received: with ECARTIS (v1.0.0; list oracle-l); Tue, 11 Nov 2014 14:06:59 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 9BED433413 for ; Tue, 11 Nov 2014 14:06:59 -0500 (EST) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dc6vfwQWWG0f for ; Tue, 11 Nov 2014 14:06:59 -0500 (EST) Received: from mail-ig0-f175.google.com (mail-ig0-f175.google.com [209.85.213.175]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 70EF933411 for ; Tue, 11 Nov 2014 14:06:32 -0500 (EST) Received: by mail-ig0-f175.google.com with SMTP id h3so1558957igd.8 for ; Tue, 11 Nov 2014 11:06:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=TwJ/plWS9obJKijWxknJXp1SB5KkIPfhCjUyNVxZh7g=; b=wnzjgc9gdcmyJZs+5HuFsoYxQ6mfLPfYd/qyRaFrUgfSK2yZF7wkEZflLae2f2//0A /iCt0aqtP5k7Z/9yGMrHmijTooDRG195aP8N6Odrv5ZJGOrTibwv4iCBwVuT+5jH9V24 lh/4UXo2ZaO0UFD/xvJ4a//SOIL8KZdqNPY/9Nqlaa0QHlI0LT4eS+QTVDcTrJQDTjxj /JLhokfbLQ7MH5xOS+gEMO/zKwsZ6rXdTYsjFcN2aPxIZpJIasWutNPh00tgy8THhKdz lt4bwRqwJ4rIPLcXiDpWojG9+SpNKfUteoysccCel4oUyaMyP66RpCHqdCObX/5qlVjs v1Eg== X-Received: by 10.107.134.89 with SMTP id i86mr19131232iod.53.1415732792503; Tue, 11 Nov 2014 11:06:32 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.132.169 with HTTP; Tue, 11 Nov 2014 11:06:12 -0800 (PST) In-Reply-To: References: From: Jared Still Date: Tue, 11 Nov 2014 11:06:12 -0800 Message-ID: Subject: Re: Oracle related configurations on Linux To: "Hameed, Amir" Cc: "oracle-l@freelists.org" Content-Type: multipart/alternative; boundary=001a113ff7a431b6b7050799faff X-archive-position: 57467 X-ecartis-version: Ecartis v1.0.0 Sender: oracle-l-bounce@freelists.org Errors-to: oracle-l-bounce@freelists.org X-original-sender: jkstill@gmail.com Precedence: normal Reply-To: jkstill@gmail.com List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: oracle-l X-List-ID: oracle-l List-subscribe: List-owner: List-post: List-archive: X-list: oracle-l --001a113ff7a431b6b7050799faff Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Nov 11, 2014 at 10:49 AM, Hameed, Amir wrote: > =C2=B7 I/O scheduler =E2=80=93 The default scheduler is Completel= y Fair > Queuing (CFQ). However, it seems that for the Oracle Unbreakable Linux > kernel, the DEADLINE I/O scheduler is the default. For Red Hat, what do > people normally set it to for highly IO intensive ERP systems? The Deadline scheduler is preferred for Databases, as the 'completely fair queuing' mechanism seems to be a misnomer when applied to databases. Here's a redhat note: https://access.redhat.com/solutions/54164 Pretty sure there are some MOS Notes re this, though it has been a few weeks since looking at schedulers, and I don't recall the notes at the moment. ... What the heck, looked one up for you: Linux: Should 'CFQ Scheduler' or 'DEADLINE Scheduler' Be Used In Oracle RAC? (Doc ID 1352304.1) Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist Principal Consultant at Pythian Pythian Blog http://www.pythian.com/blog/author/still/ Oracle Blog: http://jkstill.blogspot.com Home Page: http://jaredstill.com --001a113ff7a431b6b7050799faff Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On Tue, Nov 11, 2014 at 10:49 AM, Hameed, Amir <Amir.Hameed@xerox.com<= /a>> wrote:
=C2=B7=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 I/O scheduler =E2=80=93 The default scheduler i= s Completely Fair Queuing (CFQ). However, it seems that for the Oracle Unbr= eakable Linux kernel, the DEADLINE I/O scheduler is the default. For Red Ha= t, what do people normally set it to for highly IO intensive ERP systems?

The Deadline sc= heduler is preferred for Databases, as the 'completely fair queuing'= ; mechanism seems to be a misnomer when applied to databases.

Here's a redhat= note:=C2=A0https://a= ccess.redhat.com/solutions/54164

Pretty sure there are some MOS Notes re this= , though it has been a few weeks since looking at schedulers,
and I don't recall the notes at the moment.
...

What the heck, looked one up for you:

Linux: Should 'CFQ Scheduler' or = 'DEADLINE Scheduler' Be Used In Oracle RAC? (Doc ID 1352304.1)


Jared Still
C= ertifiable Oracle DBA and Part Time Perl Evangelist
Principal Consultan= t at Pythian
--001a113ff7a431b6b7050799faff-- -- http://www.freelists.org/webpage/oracle-l