George McCollister wrote:
I'm trying to optimize postgres performance on a headless solid state
hardware platform (no fans or disks). I have the database stored on a
USB 2.0 flash drive (hdparm benchmarks reads at 10 MB/s). Performance is
limited by the 533Mhz CPU.
Hardware:
IXP425 XScale (big e
I'm trying to optimize postgres performance on a headless solid state
hardware platform (no fans or disks). I have the database stored on a
USB 2.0 flash drive (hdparm benchmarks reads at 10 MB/s). Performance is
limited by the 533Mhz CPU.
Hardware:
IXP425 XScale (big endian) 533Mhz 64MB RAM
USB 2
On Fri, Sep 12, 2008 at 5:11 AM, Greg Smith <[EMAIL PROTECTED]> wrote:
> On Fri, 12 Sep 2008, Guillaume Cottenceau wrote:
>
> That's the main thing, and nothing else you can do will accelerate that.
> Without a useful write cache (which usually means RAM with a BBU), you'll at
> best get about 100-
On Fri, 12 Sep 2008, Guillaume Cottenceau wrote:
Out of the blue, is it just because when postgresql fsync's after a
write, on a normal system the write has to really happen on disk and
waiting for it to be complete, whereas with BBU cache the fsync is
almost immediate because the write cache
Scott Carey wrote:
Consumer drives will often read-ahead much more than server drives
optimized for i/o per second.
...
The Linux readahead setting is _definitely_ in the kernel, definitely
uses and fills the page cache, and from what I can gather, simply
issues extra I/O's to the hardware bey
On Fri, 12 Sep 2008, Matthew Wakeling wrote:
Greg, it might be worth you listing a few good RAID controllers. It's almost
an FAQ.
I started doing that at the end of
http://wiki.postgresql.org/wiki/SCSI_vs._IDE/SATA_Disks , that still needs
some work. What I do periodically is sweep through
Craig James writes:
> The performance improvement of a BB cache is amazing.
Could some of you share the insight on why this is the case? I
cannot find much information on it on wikipedia, for example.
Even http://linuxfinances.info/info/diskusage.html doesn't
explain *why*.
Out of the blue, is
On Thu, 11 Sep 2008, Greg Smith wrote:
If you want your database to perform well on writes, the first thing you do
is select a disk controller that performs well, has a well-known stable
driver for your OS, has a reasonably large cache (>=256MB), and has a battery
backup on it.
Greg, it might
