-
|
Guidance Describe the bug Complete output of one of these failed runs: `HammerDB CLI v4.8 Benchmark set to TPROC-C for PostgreSQL Value 10.2.108.3 for connection:pg_host is the same as existing value 10.2.108.3, no change made Value 5432 for connection:pg_port is the same as existing value 5432, no change made Value disable for connection:pg_sslmode is the same as existing value disable, no change made Value true for tpcc:pg_timeprofile is the same as existing value true, no change made Value true for tpcc:pg_storedprocs is the same as existing value true, no change made Value 1000 for tpcc:pg_count_ware is the same as existing value 1000, no change made Value 128 for tpcc:pg_num_vu is the same as existing value 128, no change made Value timed for tpcc:pg_driver is the same as existing value timed, no change made Value 3 for tpcc:pg_rampup is the same as existing value 3, no change made Value 15 for tpcc:pg_duration is the same as existing value 15, no change made Value true for tpcc:pg_raiseerror is the same as existing value true, no change made Value 1000000000 for tpcc:pg_total_iterations is the same as existing value 1000000000, no change made Value false for tpcc:pg_connect_pool is the same as existing value false, no change made Script loaded, Type "print script" to view Start Test(s) Vuser 2 created - WAIT IDLE Vuser 3 created - WAIT IDLE Vuser 4 created - WAIT IDLE Vuser 5 created - WAIT IDLE Vuser 6 created - WAIT IDLE Vuser 7 created - WAIT IDLE Vuser 8 created - WAIT IDLE Vuser 9 created - WAIT IDLE Logging activated 9 Virtual Users Created with Monitor VU Vuser 1:RUNNING Vuser 1:Initializing xtprof time profiler Vuser 1:Beginning rampup time of 3 minutes Vuser 2:RUNNING Vuser 2:Initializing xtprof time profiler Vuser 2:Processing 1000000000 transactions with output suppressed... Vuser 3:RUNNING Vuser 3:Initializing xtprof time profiler Vuser 3:Processing 1000000000 transactions with output suppressed... Vuser 4:RUNNING Vuser 4:Initializing xtprof time profiler Vuser 4:Processing 1000000000 transactions with output suppressed... Vuser 5:RUNNING Vuser 5:Initializing xtprof time profiler Vuser 5:Processing 1000000000 transactions with output suppressed... Vuser 6:RUNNING Vuser 6:Initializing xtprof time profiler Vuser 6:Processing 1000000000 transactions with output suppressed... Vuser 7:RUNNING Vuser 7:Initializing xtprof time profiler Vuser 7:Processing 1000000000 transactions with output suppressed... Vuser 8:RUNNING Vuser 8:Initializing xtprof time profiler Vuser 8:Processing 1000000000 transactions with output suppressed... Vuser 9:RUNNING Vuser 9:Initializing xtprof time profiler Vuser 9:Processing 1000000000 transactions with output suppressed... Vuser 1:Rampup 1 minutes complete ... Vuser 1:Rampup 2 minutes complete ... Vuser 1:Rampup 3 minutes complete ... Vuser 1:Rampup complete, Taking start Transaction Count. Vuser 1:Timing test period of 15 in minutes Vuser 1:1 ..., Vuser 1:2 ..., Vuser 1:3 ..., Vuser 1:4 ..., Vuser 1:5 ..., Vuser 1:6 ..., Vuser 1:7 ..., Vuser 1:8 ..., Vuser 1:9 ..., Vuser 1:10 ..., Vuser 1:11 ..., Vuser 1:12 ..., Vuser 1:13 ..., Vuser 1:14 ..., Vuser 1:15 ..., Vuser 1:Test complete, Taking end Transaction Count. Vuser 1:8 Active Virtual Users configured Vuser 1:TEST RESULT : System achieved 196722 NOPM from 453665 PostgreSQL TPM Vuser 1:Gathering timing data from Active Virtual Users... Vuser 8:FINISHED SUCCESS Vuser 3:FINISHED SUCCESS Vuser 4:FINISHED SUCCESS Vuser 5:FINISHED SUCCESS Vuser 9:FINISHED SUCCESS Vuser 2:FINISHED SUCCESS Vuser 7:FINISHED SUCCESS Vuser 6:FINISHED SUCCESS Vuser 1:Calculating timings... Vuser 1:Writing timing data to /tmp/hdbxtprofile_6526EE9C607703E293638373.log Vuser 1:FINISHED SUCCESS ALL VIRTUAL USERS COMPLETE vudestroy success Testing with 16 users Vuser 2 created - WAIT IDLE Vuser 3 created - WAIT IDLE Vuser 4 created - WAIT IDLE Vuser 5 created - WAIT IDLE Vuser 6 created - WAIT IDLE Vuser 7 created - WAIT IDLE Vuser 8 created - WAIT IDLE Vuser 9 created - WAIT IDLE Vuser 10 created - WAIT IDLE Vuser 11 created - WAIT IDLE Vuser 12 created - WAIT IDLE Vuser 13 created - WAIT IDLE Vuser 14 created - WAIT IDLE Vuser 15 created - WAIT IDLE Vuser 16 created - WAIT IDLE Vuser 17 created - WAIT IDLE Logging activated 17 Virtual Users Created with Monitor VU Vuser 1:RUNNING Vuser 1:Initializing xtprof time profiler Vuser 1:Beginning rampup time of 3 minutes Vuser 2:RUNNING Vuser 2:Initializing xtprof time profiler Vuser 2:Processing 1000000000 transactions with output suppressed... Vuser 3:RUNNING Vuser 3:Initializing xtprof time profiler Vuser 3:Processing 1000000000 transactions with output suppressed... Vuser 4:RUNNING Vuser 4:Initializing xtprof time profiler Vuser 4:Processing 1000000000 transactions with output suppressed... Vuser 5:RUNNING Vuser 5:Initializing xtprof time profiler Vuser 5:Processing 1000000000 transactions with output suppressed... Vuser 6:RUNNING Vuser 6:Initializing xtprof time profiler Vuser 6:Processing 1000000000 transactions with output suppressed... Vuser 7:RUNNING Vuser 7:Initializing xtprof time profiler Vuser 7:Processing 1000000000 transactions with output suppressed... Vuser 8:RUNNING Vuser 8:Initializing xtprof time profiler Vuser 8:Processing 1000000000 transactions with output suppressed... Vuser 9:RUNNING Vuser 9:Initializing xtprof time profiler Vuser 9:Processing 1000000000 transactions with output suppressed... Vuser 10:RUNNING Vuser 10:Initializing xtprof time profiler Vuser 10:Processing 1000000000 transactions with output suppressed... Vuser 11:RUNNING Vuser 11:Initializing xtprof time profiler Vuser 11:Processing 1000000000 transactions with output suppressed... Vuser 12:RUNNING Vuser 12:Initializing xtprof time profiler Vuser 12:Processing 1000000000 transactions with output suppressed... Vuser 13:RUNNING Vuser 13:Initializing xtprof time profiler Vuser 13:Processing 1000000000 transactions with output suppressed... Vuser 14:RUNNING Vuser 14:Initializing xtprof time profiler Vuser 14:Processing 1000000000 transactions with output suppressed... Vuser 15:RUNNING Vuser 15:Initializing xtprof time profiler Vuser 15:Processing 1000000000 transactions with output suppressed... Vuser 16:RUNNING Vuser 16:Initializing xtprof time profiler Vuser 16:Processing 1000000000 transactions with output suppressed... Vuser 17:RUNNING Vuser 17:Initializing xtprof time profiler Vuser 17:Processing 1000000000 transactions with output suppressed... Vuser 1:Rampup 1 minutes complete ... Vuser 1:Rampup 2 minutes complete ... Vuser 1:Rampup 3 minutes complete ... Vuser 1:Rampup complete, Taking start Transaction Count. Vuser 1:Timing test period of 15 in minutes Vuser 1:1 ..., Vuser 1:2 ..., Vuser 1:3 ..., Vuser 1:4 ..., Vuser 1:5 ..., Vuser 1:6 ..., Vuser 1:7 ..., Vuser 1:8 ..., Vuser 1:9 ..., Vuser 1:10 ..., Vuser 1:11 ..., Vuser 1:12 ..., Vuser 1:13 ..., Vuser 1:14 ..., Vuser 1:15 ..., Vuser 1:Test complete, Taking end Transaction Count. Vuser 1:16 Active Virtual Users configured Vuser 1:TEST RESULT : System achieved 379697 NOPM from 877211 PostgreSQL TPM Vuser 1:Gathering timing data from Active Virtual Users... Vuser 2:FINISHED SUCCESS Vuser 10:FINISHED SUCCESS Vuser 6:FINISHED SUCCESS Vuser 5:FINISHED SUCCESS Vuser 4:FINISHED SUCCESS Vuser 11:FINISHED SUCCESS Vuser 8:FINISHED SUCCESS Vuser 7:FINISHED SUCCESS Vuser 12:FINISHED SUCCESS Vuser 3:FINISHED SUCCESS Vuser 13:FINISHED SUCCESS Vuser 16:FINISHED SUCCESS Vuser 17:FINISHED SUCCESS Vuser 9:FINISHED SUCCESS Vuser 1:Calculating timings... Vuser 14:FINISHED SUCCESS Vuser 1:Writing timing data to /tmp/hdbxtprofile_6526F2F8607703E253230373.log Vuser 15:FINISHED SUCCESS Virtual Users remain running in background or shutting down, retry Testing with 32 users Virtual Users still active in background Enter yes or no: replied yes Error: can't read "threadscreated(0)": no such variable Virtual Users remain running in background or shutting down, retry Testing with 64 users Virtual Users still active in background Enter yes or no: replied yes Error: can't read "threadscreated(0)": no such variable Virtual Users remain running in background or shutting down, retry Testing with 128 users Virtual Users still active in background Enter yes or no: replied yes Error: can't read "threadscreated(0)": no such variable Virtual Users remain running in background or shutting down, retry Testing with 256 users Virtual Users still active in background Enter yes or no: replied yes Error: can't read "threadscreated(0)": no such variable Virtual Users remain running in background or shutting down, retry Tests complete` To Reproduce
Expected behavior Screenshots
Test run script: puts "Start Test(s)" HammerDB Version (please complete the following information):
HammerDB Interface (please complete the following information):
Operating System (please complete the following information):
Database Server (please complete the following information):
Database Client (please complete the following information):
Additional context |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 10 replies
-
|
When we close down the Virtual Users after the 16 virtual User run, we get the message:
If we put the data in order, you can see that Virtual User 1 hasn't finished before we call vudestroy So, we need to give it more time and there are a couple of things we can do: As a quick fix you can put the or the correct way in generic.xml - there is a variable called xt_gather_timeout specifically for this purpose. Note that if you can change the XML value you will need to remove the generic.db SQLite database file in your temp area to re-read it. Or for advanced users to set it directly, run a command such as follows either at the CLI prompt or in the console of the HammerDB GUI. You can see that xt_gather_timeout is now set to 60, this will then mean that HammerDB will wait for 60 seconds for the writing of the timing data. |
Beta Was this translation helpful? Give feedback.
-
|
Alessandro - yes, good to hear from you, So yes, there are 2 settings in the XML configuration that control timeouts. The first is xt_gather_timeout for the time for all virtual users to report back their own individual timings to the main thread and the second one is the time for the main thread to wait for the virtual users to finish when running in the command line, by default these are both set to 10. Being set in the XML configuration, you either need to change this and remove the existing SQLite .db files to pick up the changes or in v4.9 you can go in directly and change the settings manually with the following commands: (example change from 10 seconds to 60 seconds) As this is less than intuitive, a change is already coming in the next version to add a "giset" command to modify generic settings and a print generic command here #646 You can use this now by building from source to pikc up all the latest changes which is very easy to do https://www.hammerdb.com/blog/uncategorized/how-to-build-hammerdb-from-source/. Note that you can build just for one database if you wish so you don't need to install the libraries for all the ones you are not interested in just by commenting the unwanted ones out in the Setup file in the build directory. |
Beta Was this translation helpful? Give feedback.
-
|
That worked just fine. I just set the parameters directly into the ingested tcl file and all seems working fine. |
Beta Was this translation helpful? Give feedback.
-
|
For completeness for anyone reading just the end of the thread: |
Beta Was this translation helpful? Give feedback.
-
|
Hi @sm-shaw So that I understand once I eventually switch to 4.10+ Instead of using a command like Instead use this |
Beta Was this translation helpful? Give feedback.
-
|
Yes, that is correct the change is described here: #646 |
Beta Was this translation helpful? Give feedback.
When we close down the Virtual Users after the 16 virtual User run, we get the message:
Virtual Users remain running in background or shutting down, retryIf we put the data in order, you can see that Virtual User 1 hasn't finished before we call vudestroy