On Thu, Jan 27, 2011 at 6:05 PM, Scott Marlowe scott.marl...@gmail.com wrote:
A good method to start is to log long running queries and then explain
analyze just them.
We are already doing the logging part, we are just a bit behind on the
explain analyze part of things. One day soon...
Thanks,
Hi all,
we are running a fairly big Ruby on Rails application on Postgres 8.4.
Our traffic grew quite a bit lately, and since then we are facing DB
performance issues. System load occasionally explodes (around 170
yesterday on a 16 core system), which seems to be caused by disk I/O
(iowait in our
Cédric, thanks a lot for your answer so far!
On Thu, Jan 27, 2011 at 12:24 PM, Cédric Villemain
cedric.villemain.deb...@gmail.com wrote:
you have swap used, IO on the swap partition ?
Memory-wise we are fine.
can you paste the /proc/meminfo ?
Sure:
# cat /proc/meminfo
MemTotal:
On Thu, Jan 27, 2011 at 1:30 PM, Justin Pitts justinpi...@gmail.com wrote:
That is a foot-gun waiting to go off.
Thanks, I had already changed this after Cedric's mail.
HDD: 2x 120 GB OCZ Vertex 2 SSD; RAID 1
random_page_cost = 2.0
I thought these drives were a lot better at random IO than
On Thu, Jan 27, 2011 at 4:06 PM, Andy Colson a...@squeakycode.net wrote:
Have you run each of your queries through explain analyze lately?
A code review including checking of queries is on our agenda.
You are vacuuming/autovacuuming, correct?
Sure :-)
Thank you,
Michael
--
Sent via