| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: raid array seek performance |
| Date: | 2011-09-14 18:18:49 |
| Message-ID: | CAHyXU0zGOKhY3H_giqz2=39cLzGccFwVYnS7Ag9coiWpt0RKMQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Wed, Sep 14, 2011 at 2:44 AM, Greg Smith <greg(at)2ndquadrant(dot)com> wrote:
> If you want to get a useful measurement of seeks/second, setup pgbench-tools
> with a SELECT-only test, and create a database that's 2 to 4X as big as RAM.
> The TPS result you get from that is a much more useful number for
> real-world seeks than this.
A thought on that note: it sure would be nice if you could define
scaling factor in terms of data size instead of linear multiples of
100000, something like:
pgbench -i -x 64gb
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Igor Neyman | 2011-09-14 19:40:07 | Re: Migrated from 8.3 to 9.0 - need to update config (re-post) |
| Previous Message | Gunnlaugur Þór Briem | 2011-09-14 17:53:22 | Constraint exclusion on UNION ALL subqueries with WHERE conditions |