stanimir petrov wrote:
> Now the servers are dual core CPU 2.6 with 1.7 GB RAM and i standart
> disk. (the small instance from AWS)
You're never going to be able to tune for writing data fast on a AWS
environment; there just isn't enough disk throughput available. If this
application really does take off the way you expect it to, don't be
surprised to find you have to move it to real hardware to keep up.
Dedicated database servers tend to have tens of disks in them to keep up
with the sort of load you're expecting, and you just can't get that in a
cloud environment. You can do some work to improve I/O using multiple
is a good introduction to that.
The basic tuning advice you're looking for is available at
If you are trying to get faster writes out of AWS hardware, you may have
to turn off synchronous_commit to accomplish that. That has some
potential lost transaction downsides, but simple disks just can't write
data that fast so it may be the only way to make this work well.
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
In response to
pgsql-performance by date
|Next:||From: Kneringer, Armin||Date: 2010-07-21 16:47:54|
|Subject: Re: potential performance gain by query planner
|Previous:||From: Greg Smith||Date: 2010-07-21 14:59:53|
|Subject: Re: Using more tha one index per table|