From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | possible effective_io_concurrency performance regression |
Date: | 2017-07-21 19:42:11 |
Message-ID: | e9d8ed18-057e-7a89-7f82-8e8c8ad3c455@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
-hackers,
While updating my Postgres performance curriculum I was doing some
testing with effective_io_concurrency and I may have found a regression.
I am aware that the parameter only works under certain conditions.
However, what I appear to have found is that if it is set to anything
but 0, it is a regression for (at least benchmarksql tpc-c) workloads.
See here:
Testing with the TPC style benchmark shows that on local systems,
setting this between 0 – 48 keeps the TPS within noise level. However,
testing also shows that on cloud systems such as Google Cloud Compute
setting this setting to anything greater than 0 results in an
approximately 10% performance degradation on TPS:
Local/GCE effective_io_concurrency TPS
GCE OFF 47951
8 43098
1 43233
LOCAL
0 9939
4 9960
16 9955
48 9958
I was able to produce these results pretty consistently. I wonder if any
has seen this on EBS? GCE instance is 16CPU, 59GB memory, 240MB
Sustained rate SSD with 15k IOPS.
Thanks,
JD
--
Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc
PostgreSQL Centered full stack support, consulting and development.
Advocate: @amplifypostgres || Learn: https://pgconf.us
***** Unless otherwise stated, opinions are my own. *****
From | Date | Subject | |
---|---|---|---|
Next Message | Mat Arye | 2017-07-21 20:17:48 | Syncing sql extension versions with shared library versions |
Previous Message | Alvaro Herrera | 2017-07-21 19:35:28 | Re: Locale dependency in new postgres_fdw test |