| From: | Jeff <threshar(at)torgo(dot)978(dot)org> |
|---|---|
| To: | Albe Laurenz *EXTERN* <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
| Cc: | "Grzegorz Jaskiewicz *EXTERN*" <gryzman(at)gmail(dot)com>, "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>, "Mark Wong" <markwkm(at)gmail(dot)com>, <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: linux deadline i/o elevator tuning |
| Date: | 2009-04-13 14:13:15 |
| Message-ID: | 7D33317A-51F4-42B4-AA61-5C7D4CBE0AF4@torgo.978.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Apr 10, 2009, at 2:47 AM, Albe Laurenz *EXTERN* wrote:
> 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.
>
This is my experience as well, I posted about playing with the
scheduler a while ago on -performance, but I can't seem to find it.
If you have a halfway OK raid controller, CFQ is useless. You can fire
up something such as pgbench or pgiosim, fire up an iostat and then
watch your iops jump high when you flip to noop or deadline and
plummet on cfq. Try it. it's neat!
--
Jeff Trout <jeff(at)jefftrout(dot)com>
http://www.stuarthamm.net/
http://www.dellsmartexitin.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2009-04-13 15:18:16 | Re: linux deadline i/o elevator tuning |
| Previous Message | Justin Pitts | 2009-04-13 13:42:59 | Re: Postgres 8.x on Windows Server in production |