| From: | Mark Wong <markw(at)osdl(dot)org> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | testperf-general(at)pgfoundry(dot)org, "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [Testperf-general] pg_autovacuum w/ dbt2 |
| Date: | 2005-01-07 18:29:23 |
| Message-ID: | 20050107102923.B16495@osdl.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-www |
On Fri, Jan 07, 2005 at 10:13:52AM -0800, Josh Berkus wrote:
> Mark,
>
> > All default parameters. Matthew also recommended using the
> > vacuum_delay setting so I was about to try that.
>
> Interesting ... the default parameters are quite conservative, running only
> when the table has doubled in new rows. So if those spikes are vacuums,
> then the DBT2 test is updating or adding 100% of the rows in the orders table
> every 6-8 minutes? Does that seem right?
>
Some hand-wavey math here:
We start with 18,000,000 rows in the orders table.
Based one 3281 transactions per minute for just the new-order transaction:
288 transactions per minute for delivery
New-order inserts 3281 rows per minute (not counting the 1% of rollbacks.)
Delivery updates 288 rows per minute in orders.
So no, we're not change that many rows per minute...
Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2005-01-07 18:45:22 | Re: PostgreSQL 8.0.0 Release Candidate 4 |
| Previous Message | Andreas Pflug | 2005-01-07 18:23:00 | Re: Compiere ERP and SQL quirks |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2005-01-07 19:13:01 | Torrents |
| Previous Message | Josh Berkus | 2005-01-07 18:13:52 | Re: [Testperf-general] pg_autovacuum w/ dbt2 |