From: | Bill McGonigle <bill(at)bfccomputing(dot)com> |
---|---|
To: | Greg Stark <gsstark(at)mit(dot)edu> |
Cc: | stange(at)rentec(dot)com, Dave Cramer <pg(at)fastcrypt(dot)com>, Joshua Marsh <icub3d(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org, Luke Lonergan <llonergan(at)greenplum(dot)com> |
Subject: | Re: Hardware/OS recommendations for large databases ( |
Date: | 2005-11-21 19:58:18 |
Message-ID: | 8c110ae5a3902fba586f3353b25fc54f@bfccomputing.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Would it be worth first agreeing on a common set of criteria to
measure? I see many data points going back and forth but not much
agreement on what's worth measuring and how to measure.
I'm not necessarily trying to herd cats, but it sure would be swell to
have the several knowledgeable minds here come up with something that
could uniformly tested on a range of machines, possibly even integrated
into pg_bench or something. Disagreements on criteria or methodology
should be methodically testable.
Then I have dreams of a new pg_autotune that would know about these
kinds of system-level settings.
I haven't been on this list for long, and only using postgres for a
handful of years, so forgive it if this has been hashed out before.
-Bill
-----
Bill McGonigle, Owner Work: 603.448.4440
BFC Computing, LLC Home: 603.448.1668
bill(at)bfccomputing(dot)com Mobile: 603.252.2606
http://www.bfccomputing.com/ Pager: 603.442.1833
Jabber: flowerpt(at)gmail(dot)com Text: bill+text(at)bfccomputing(dot)com
Blog: http://blog.bfccomputing.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Stone | 2005-11-21 19:59:09 | Re: Hardware/OS recommendations for large databases ( |
Previous Message | Alvaro Herrera | 2005-11-21 19:51:47 | Re: Hardware/OS recommendations for large databases ( |