From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Checkpoint cost, looks like it is WAL/CRC |
Date: | 2005-07-22 18:01:07 |
Message-ID: | 200507221101.07849.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom,
> This will remove just the CRC calculation work associated with backed-up
> pages. Note that any attempt to recover from the WAL will fail, but I
> assume you don't need that for the purposes of the test run.
Looks like the CRC calculation work isn't the issue. I did test runs of
no-CRC vs. regular DBT2 with different checkpoint timeouts, and didn't
discern any statistical difference. See attached spreadsheet chart (the
two different runs are on two different machines).
I think this test run http://khack.osdl.org/stp/302903/results/0/, with a
30-min checkpoint shows pretty clearly that the behavior of the
performance drop is consistent with needing to "re-prime" the WAL will
full page images. Each checkpoint drops performance abruptly, and then
slowly recovers until the next checkpoint.
Do note that there is a significant statistical variation in individual
runs. It's only the overall trend which is significant.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
Attachment | Content-Type | Size |
---|---|---|
crc_patch_test.pdf | application/pdf | 20.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-07-22 18:06:17 | Re: [HACKERS] Planner doesn't look at LIMIT? |
Previous Message | Vivek Khera | 2005-07-22 17:34:49 | Re: Problems compiling Postgresql 8.0.3 on 10.4 |