Postgres Professional
   

Re: linux deadline i/o elevator tuning

From: Albe Laurenz *EXTERN*
Subject: Re: linux deadline i/o elevator tuning
Date: ,
Msg-id: D960CB61B694CF459DCFB4B0128514C202FF655A@exadv11.host.magwien.gv.at
(view: Whole thread, Raw)
In response to: Re: linux deadline i/o elevator tuning  (Grzegorz Jaśkiewicz)
Responses: Re: linux deadline i/o elevator tuning  (Jeff)
List: pgsql-performance

Tree view

linux deadline i/o elevator tuning  (Mark Wong, )
 Re: linux deadline i/o elevator tuning  ("Kevin Grittner", )
  Re: linux deadline i/o elevator tuning  (Grzegorz Jaśkiewicz, )
   Re: linux deadline i/o elevator tuning  (Matthew Wakeling, )
    Re: linux deadline i/o elevator tuning  (Grzegorz Jaśkiewicz, )
     Re: linux deadline i/o elevator tuning  ("Kevin Grittner", )
      Re: linux deadline i/o elevator tuning  (Grzegorz Jaśkiewicz, )
     Re: linux deadline i/o elevator tuning  (Matthew Wakeling, )
    Re: linux deadline i/o elevator tuning  ("Kevin Grittner", )
   Re: linux deadline i/o elevator tuning  (Scott Carey, )
   Re: linux deadline i/o elevator tuning  ("Albe Laurenz *EXTERN*", )
    Re: linux deadline i/o elevator tuning  (Jeff, )
     Re: linux deadline i/o elevator tuning  ("Kevin Grittner", )
  Re: linux deadline i/o elevator tuning  (Arjen van der Meijden, )
   Re: linux deadline i/o elevator tuning  ("Kevin Grittner", )
 Re: linux deadline i/o elevator tuning  (Mark Wong, )
  Re: linux deadline i/o elevator tuning  (Mark Wong, ) 
Grzegorz Jaskiewicz wrote:
> acording to kernel folks, anticipatory scheduler is even better for dbs.
> Oh well, it probably means everyone has to test it on their own at the
> end of day.

In my test case, noop and deadline performed well, deadline being a little
better than noop.

Both anticipatory and CFQ sucked big time.

Yours,
Laurenz Albe

pgsql-performance by date:

Previous:
From: Ognjen Blagojevic
Date:
Subject: Postgres 8.x on Windows Server in production
Next:
From: Tom Lane
Date:
Subject: Re: Nested query performance issue