From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Why is checkpoint so costly? |
Date: | 2005-06-21 19:00:56 |
Message-ID: | 200506211200.56188.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Folks,
Going over some performance test results at OSDL, our single greatest
performance issue seems to be checkpointing. Not matter how I fiddle
with it, checkpoints seem to cost us 1/2 of our throughput while they're
taking place. Overally, checkpointing costs us about 25% of our
performance on OLTP workloads.
Example: http://khack.osdl.org/stp/302671/results/0/
Can we break down everything that happens during a checkpoint so that we
can see where this huge cost is coming from? Checkpointing should be
limited to fsyncing to disk and marking WAL files as recyclable, but there
seems to be something more.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2005-06-21 19:06:12 | Re: Function's LEAST, GREATEST and DECODE (Oracle vararg |
Previous Message | Bruce Momjian | 2005-06-21 18:46:36 | Re: Function's LEAST, GREATEST and DECODE (Oracle vararg polymorphic |