From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Jan Wieck <JanWieck(at)Yahoo(dot)com>, testperf-general(at)pgfoundry(dot)org |
Subject: | Re: [Testperf-general] BufferSync and bgwriter |
Date: | 2004-12-15 17:43:53 |
Message-ID: | 200412150943.53578.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Folks,
> To allow DBT2 to be used for real bgwriter benchmarking, Mark would need to
> change the following:
>
> 1) Randomize the timing of the commits, so that sometimes there is only 30
> writes/minute, and other times there is 300. A timing pattern that would
> produce a "sine wave" with occasional random spikes would be best; in my
> experience, OLTP applications tend to have wave-like spikes and lulls.
>
> 2) Include a sprinkling of random or regular "large writes" which affect
> several tables and 1000's of rows. For example, once per hour, change
> 10,000 pending orders to "shipped", and archive 10,000 "old orders" to an
> archive table.
Oh, also we need to:
3) Run the test for 3+ hours after scaling up, and turn on autovacuum.
--
Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | simon | 2004-12-15 18:24:01 | Re: Re: [Testperf-general] BufferSync and bgwriter |
Previous Message | Josh Berkus | 2004-12-15 17:36:53 | Re: [Testperf-general] BufferSync and bgwriter |