From: | Greg Smith <greg(at)2ndquadrant(dot)com> |
---|---|
To: | Samuel Gendler <sgendler(at)ideasculptor(dot)com> |
Cc: | Joshua Tolley <eggyknap(at)gmail(dot)com>, Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, mladen(dot)gogala(at)vmsinfo(dot)com, Neil Whelchel <neil(dot)whelchel(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Slow count(*) again... |
Date: | 2010-10-12 06:39:32 |
Message-ID: | 4CB402A4.9070109@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
Samuel Gendler wrote:
> I spent some time going through the various tuning docs on the wiki
> whie bringing some new hardware up and I can't remember seeing any
> discussion of tweaking read-ahead at all in the normal
> performance-tuning references. Do you have any documentation of the
> kinds of tweaking you have done and its effects on different types of
> workloads?
Much of my recent research has gone into the book you'll see plugged
below rather than the wiki. The basics of read-ahead tuning is that you
can see it increase bonnie++ sequential read results when you increase
it, to a point. Get to that point and stop and you should be in good shape.
--
Greg Smith, 2ndQuadrant US greg(at)2ndQuadrant(dot)com Baltimore, MD
PostgreSQL Training, Services and Support www.2ndQuadrant.us
Author, "PostgreSQL 9.0 High Performance" Pre-ordering at:
https://www.packtpub.com/postgresql-9-0-high-performance/book
From | Date | Subject | |
---|---|---|---|
Next Message | Devrim GÜNDÜZ | 2010-10-12 07:49:57 | Re: pgxs docdir question |
Previous Message | Greg Smith | 2010-10-12 06:32:09 | Re: Slow count(*) again... |
From | Date | Subject | |
---|---|---|---|
Next Message | Vitalii Tymchyshyn | 2010-10-12 07:56:13 | Re: Slow count(*) again... |
Previous Message | Greg Smith | 2010-10-12 06:32:09 | Re: Slow count(*) again... |