| From: | Chris <chris(at)bitmead(dot)com> |
|---|---|
| To: | Matthias Urlichs <smurf(at)noris(dot)net> |
| Cc: | Hannu Krosing <hannu(at)tm(dot)ee>, The Hermit Hacker <scrappy(at)hub(dot)org>, Alessio Bragadini <alessio(at)albourne(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Performance (was: The New Slashdot Setup (includes MySql server)) |
| Date: | 2000-05-19 19:54:20 |
| Message-ID: | 39259BEC.3777E935@bitmead.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
> > > That being said, the standard MySQL benchmark _still_ is 30 times
> > > faster for MySQL 3.23 than on PostgreSQL 7.0 (with fsync turned off,
> > > _and_ nonstandard speed-up PostgreSQL features like VACUUM enabled,
VACUUM is not a speed-up feature, it's a slow-down feature. It reclaims
space and that takes time. It does update system statistics which can
help performance if done after a data load or perhaps once a day.
But "sprinkling the code" with vacuum sounds like a big performance
killer. Hope you are not counting vacuum as part of your 1000 read()
calls.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris | 2000-05-19 20:34:06 | Re: Performance (was: The New Slashdot Setup (includes MySql server)) |
| Previous Message | Bruce Momjian | 2000-05-19 19:52:44 | Re: Performance (was: The New Slashdot Setup (includes MySql server)) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-05-19 20:08:15 | Re: Re: Heaps of read() syscalls by the postmaster |
| Previous Message | Bruce Momjian | 2000-05-19 19:52:44 | Re: Performance (was: The New Slashdot Setup (includes MySql server)) |