From: | "Kevin Grittner" <kgrittn(at)mail(dot)com> |
---|---|
To: | "Niels Kristian Schjødt" <nielskristian(at)autouncle(dot)com>,sthomas(at)optionshouse(dot)com |
Cc: | "Willem Leenen" <willem_leenen(at)hotmail(dot)com>,pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Optimize update query |
Date: | 2012-11-30 01:24:26 |
Message-ID: | 20121130012426.69300@gmx.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Niels Kristian Schjødt wrote:
> Okay, now I'm done the updating as described above. I did the
> postgres.conf changes. I did the kernel changes, i added two
> SSD's in a software RAID1 where the pg_xlog is now located -
> unfortunately the the picture is still the same :-(
You said before that you were seeing high disk wait numbers. Now it
is zero accourding to your disk utilization graph. That sounds like
a change to me.
> When the database is under "heavy" load, there is almost no
> improvement to see in the performance compared to before the
> changes.
In client-visible response time and throughput, I assume, not
resource usage numbers?
> A lot of both read and writes takes more than a 1000 times as
> long as they usually do, under "lighter" overall load.
As an odd coincidence, you showed your max_connections setting to
be 1000.
http://wiki.postgresql.org/wiki/Number_Of_Database_Connections
-Kevin
From | Date | Subject | |
---|---|---|---|
Next Message | Niels Kristian Schjødt | 2012-11-30 01:43:00 | Re: Optimize update query |
Previous Message | Niels Kristian Schjødt | 2012-11-30 00:59:00 | Re: Optimize update query |