On Fri, Apr 1, 2016 at 2:09 PM, Andres Freund <and...@anarazel.de> wrote:
> One interesting thing to do would be to use -P1 during the test and see > how much the performance varies over time. > I have run with -P option, I ran for 1200 second and set -P as 30 second, and what I observed is that when its low its low throughout the run and when its high, Its high for complete run. Non Default Parameter: -------------------------------- shared_buffer 8GB Max Connections 150 ./pgbench -c $threads -j $threads -T 1200 -M prepared -S -P 30 postgres Test results are attached in result.tar file. File details: ------------------ 1. head_run1.txt --> 20 mins run on head reading 1 2. head_run2.txt --> 20 mins run on head reading 2 3. head_patch_run1.txt --> 20 mins run on head + patch reading 1 4. head_patch_run2.txt --> 20 mins run on head + patch reading 2 5. head_pinunpin.txt --> 20 mins run on head + pinunpin-cas-8.patch 6. head_pinunpin_patch.txt --> 20 mins run on head + pinunpin-cas-8.patch + patch reading -- Regards, Dilip Kumar EnterpriseDB: http://www.enterprisedb.com
result.tar
Description: Unix tar archive
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
