On 12.04.2007, at 07:26, Ron wrote:
> You need to buy RAM and HD.
Before he does that, wouldn't it be more useful, to find out WHY he
has so much IO?
Have I missed that or has nobody suggested finding the slow queries
(when you have much IO on them, they might be slow at least with a
high shared memory setting).
So, my first idea is, to turn on query logging for queries longer
than a xy milliseconds, "explain analyse" these queries and see
wether there are a lot of seq scans involved, which would explain the
Just an idea, perhaps I missed that step in that discussion
But yes, it might also be, that the server is swapping, that's
another thing to find out.
In response to
pgsql-performance by date
|Next:||From: Ron||Date: 2007-04-12 14:59:10|
|Subject: Re: Slow Postgresql server|
|Previous:||From: Merlin Moncure||Date: 2007-04-12 13:42:03|
|Subject: Re: Large objetcs performance|
pgsql-hackers by date
|Next:||From: Jonah H. Harris||Date: 2007-04-12 14:08:11|
|Subject: Re: Benchmarking tools for the Postgres, EDB and Oracle Database|
|Previous:||From: Alvaro Herrera||Date: 2007-04-12 14:07:22|
|Subject: Re: What tools do people use to hack on PostgreSQL?|
pgsql-patches by date
|Next:||From: Alvaro Herrera||Date: 2007-04-12 14:58:16|
|Subject: Re: autovacuum multiworkers, patch 5|
|Previous:||From: Tom Lane||Date: 2007-04-12 13:29:52|
|Subject: Re: [HACKERS] Fix mdsync never-ending loop problem |