| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Scaling shared buffer eviction |
| Date: | 2014-05-17 03:31:51 |
| Message-ID: | CAA4eK1LFxvfuef_7N_Lo43d6-Nu1Kw08MgNUeL3x1mnU6TharQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, May 17, 2014 at 6:29 AM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
>
>
> On Fri, May 16, 2014 at 7:51 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
wrote:
>>
>> shared_buffers= 8GB
>> scale factor = 3000
>> RAM - 64GB
>
> I'm having a little trouble following this. These figure are transactions
per second for a 300 second pgbench tpc-b run?
Yes, the figures are tps for a 300 second run.
It is for select-only transactions.
What does "Thrds" denote?
It denotes number of threads (-j in pgbench run)
I have used below statements to take data
./pgbench -c 64 -j 64 -T 300 -S postgres
./pgbench -c 128 -j 128 -T 300 -S postgres
The reason for posting the numbers for 64/128 threads is because we have
mainly concurrency bottleneck when the number of connections are higher
than CPU cores and I am using 16 cores, 64 hardware threads m/c.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2014-05-17 04:54:26 | Re: Scaling shared buffer eviction |
| Previous Message | Peter Geoghegan | 2014-05-17 00:59:06 | Re: Scaling shared buffer eviction |