| From: | KONDO Mitsumasa <kondo(dot)mitsumasa(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Tasos Petalas <tasos(dot)petalas(at)upstreamsystems(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: PG performance issues related to storage I/O waits |
| Date: | 2013-08-01 02:02:06 |
| Message-ID: | 51F9C19E.7010105@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Hi Tasos,
(2013/07/31 20:58), Tasos Petalas wrote:
> We have set synchronous_commit to off but since almost all of application queries
> are using prepared statements we don't get any real benefit.
> Also please advise on any postgres.conf modification that could significantly
> affect storage load (WAL-checkpoint configuration etc.)
Please send us to your postgresql.conf and detail of your server (memory ,raid
cache size and OS version).
I think your server's memory is big. You should set small dirty_background_ratio
or dirty_background_byte. If your server's memory is big, PostgreSQL's checkpoint
executes stupid disk-write.
By the way, I make new checkpoint scheduler and method now. If you could send
more detail information which is like response time or load average, you will
help me to make better my patch.
Best regards,
--
Mitsumasa KONDO
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergey Burladyan | 2013-08-01 09:55:07 | Looks like merge join planning time is too big, 55 seconds |
| Previous Message | Greg Smith | 2013-07-31 16:02:50 | Re: Fw: [osdldbt-general] Running DBT5 on remote database server |