| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: latest pgbench results |
| Date: | 2013-08-06 17:37:34 |
| Message-ID: | 5201345E.5070008@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 08/06/2013 08:26 AM, Robert Haas wrote:
> Here are the latest pgbench results from the IBM POWER7 machine.
> These results were gathered about two weeks ago. I ran each test
> configuration three times; below I report the median of the three
> results. For all runs, I used scale factor = 300, clients = jobs, and
> the following non-default configuration parameters: shared_buffers =
> 8GB, maintenance_work_mem = 4GB, synchronous_commit = off,
> checkpoint_segments = 300, checkpoint_timeout = 15min,
> checkpoint_completion_target = 0.9, log_line_prefix = '%t [%p] '.
> Commits in use were cce5d681be7abfd9f48c28151ebf2b242f8ba438,
> dd8ea2eb5e996f3f3dfd928e20aa2462c4bd9c63,
> cce5d681be7abfd9f48c28151ebf2b242f8ba438.
What's the length of the run each time?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2013-08-06 17:41:48 | Re: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review]) |
| Previous Message | Josh Berkus | 2013-08-06 17:33:20 | Re: Disabling ALTER SYSTEM SET WAS: Re: ALTER SYSTEM SET command to change postgresql.conf parameters |