| From: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "Robert Haas *EXTERN*" <robertmhaas(at)gmail(dot)com>, "Greg Stark" <stark(at)mit(dot)edu> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: measuring lwlock-related latency spikes |
| Date: | 2012-04-02 07:11:00 |
| Message-ID: | D960CB61B694CF459DCFB4B0128514C207B2C39E@exadv11.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas wrote:
> I suppose one interesting question is to figure out if there's a way I
> can optimize the disk configuration in this machine, or the Linux I/O
> scheduler, or something, so as to reduce the amount of time it spends
> waiting for the disk.
I'd be curious to know if using the deadline scheduler will improve
things. I have experienced pretty bad performance with cfq under
load, where sequential table scans were starved to the point where
they took hours instead of less than a minute (on an idle system).
But I believe that also depends a lot on the storage system used.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2012-04-02 07:15:20 | Re: measuring lwlock-related latency spikes |
| Previous Message | David Johnston | 2012-04-02 05:40:06 | Re: Switching to Homebrew as recommended Mac install? |