8. Run the workload

To begin the workload type vurun. The test runs as per the configuration and reports the result at the end and the Virtual User status.

hammerdb>vurun
Script loaded, Type "print script" to view
Vuser 1 created MONITOR - WAIT IDLE
Vuser 2 created - WAIT IDLE
Vuser 3 created - WAIT IDLE
Vuser 4 created - WAIT IDLE
Vuser 5 created - WAIT IDLE
Logging activated
to C:/temp/hammerdb.log
5 Virtual Users Created with Monitor VU
Vuser 1:RUNNING
Vuser 1:DBVersion:16.0.1135.2
Vuser 1:Beginning rampup time of 1 minutes
Vuser 2:RUNNING
Vuser 2:Processing 10000000 transactions with output suppressed...
Vuser 3:RUNNING
Vuser 3:Processing 10000000 transactions with output suppressed...
Vuser 4:RUNNING
Vuser 4:Processing 10000000 transactions with output suppressed...
Vuser 5:RUNNING
Vuser 5:Processing 10000000 transactions with output suppressed...
Vuser 1:Rampup 1 minutes complete ...
Vuser 1:Rampup complete, Taking start Transaction Count.
Vuser 1:Timing test period of 3 in minutes
Vuser 1:1 ...,
Vuser 1:2 ...,
Vuser 1:3 ...,
Vuser 1:Test complete, Taking end Transaction Count.
Vuser 1:4 Active Virtual Users configured
Vuser 1:TEST RESULT : System achieved 264796 NOPM from 616230 SQL Server TPM
Vuser 1:FINISHED SUCCESS
Vuser 5:FINISHED SUCCESS
Vuser 3:FINISHED SUCCESS
Vuser 4:FINISHED SUCCESS
Vuser 2:FINISHED SUCCESS
ALL VIRTUAL USERS COMPLETE
Benchmark Run jobid=67FD28A55F8F03E223834333

To complete the test type vudestroy.

hammerdb>vudestroy
vudestroy success

and clear the script.

hammerdb>clearscript
Script cleared

The CLI supports a transaction counter with the same settings as the GUI.

hammerdb>tcset
Usage: tcset [refreshrate|logtotemp|unique|timestamps] value

and CPU metrics again with the same settings as the GUI.

hammerdb>metset
Usage: metset [agent_hostname|agent_id] value

The transaction counter and metrics can be run with the tcstart and metstart commands respectively. When these are running transactions and metrics will be collected in the job output.

hammerdb>tcstart
Transaction Counter Started
hammerdb>0 MSSQLServer tpm
hammerdb>metstart
Starting Local Metrics Agent on raven
after#244
hammerdb>Initializing HammerDB Metric Agent 5.0
HammerDB Metric Agent active @ id 27768 hostname raven (Ctrl-C to Exit)
Connecting to Agent to Display CPU Metrics
Metric receive port open @ 15748 on raven
Connecting to HammerDB Agent @ raven:27768
Testing Agent Connectivity...OK
Received a new display request from host fe80::a3b7:309e:a58d:3658%11
Metrics Connected
New display accepted @ 15748 raven
Prepared CPU metrics for Intel(R) Core(TM) i9-14900KS
12 MSSQLServer tpm
Started CPU Metrics for Intel(R) Core(TM) i9-14900KS:(32 CPUs)
Sending CPU metrics to 15748 raven ...connection established
hammerdb>vurun
Script loaded, Type "print script" to view
Vuser 1 created MONITOR - WAIT IDLE
Vuser 2 created - WAIT IDLE
Vuser 3 created - WAIT IDLE
Vuser 4 created - WAIT IDLE
Vuser 5 created - WAIT IDLE
Logging activated
to C:/temp/hammerdb.log
5 Virtual Users Created with Monitor VU
Vuser 1:RUNNING
Vuser 1:DBVersion:16.0.1135.2
Vuser 1:Beginning rampup time of 1 minutes
Vuser 2:RUNNING
Vuser 2:Processing 10000000 transactions with output suppressed...
Vuser 3:RUNNING
Vuser 3:Processing 10000000 transactions with output suppressed...
Vuser 4:RUNNING
Vuser 4:Processing 10000000 transactions with output suppressed...
Vuser 5:RUNNING
Vuser 5:Processing 10000000 transactions with output suppressed...
CPU all usr%-0.00 sys%-0.00 irq%-0.00 idle%-0.00
339216 MSSQLServer tpm
CPU all usr%-9.64 sys%-1.23 irq%-0.22 idle%-89.01
707682 MSSQLServer tpm
CPU all usr%-9.48 sys%-1.39 irq%-0.27 idle%-89.25
700632 MSSQLServer tpm
CPU all usr%-9.55 sys%-1.09 irq%-0.15 idle%-88.92
675360 MSSQLServer tpm
CPU all usr%-10.52 sys%-1.29 irq%-0.25 idle%-88.38
759096 MSSQLServer tpm
CPU all usr%-10.14 sys%-1.26 irq%-0.19 idle%-88.48
726372 MSSQLServer tpm
Vuser 1:Rampup 1 minutes complete ...
Vuser 1:Rampup complete, Taking start Transaction Count.
Vuser 1:Timing test period of 3 in minutes
CPU all usr%-10.04 sys%-1.27 irq%-0.23 idle%-88.69
741852 MSSQLServer tpm
CPU all usr%-10.84 sys%-1.30 irq%-0.26 idle%-87.94
738720 MSSQLServer tpm
CPU all usr%-10.26 sys%-1.36 irq%-0.21 idle%-88.16
707208 MSSQLServer tpm
CPU all usr%-10.31 sys%-1.29 irq%-0.19 idle%-87.94
736344 MSSQLServer tpm
CPU all usr%-10.49 sys%-1.31 irq%-0.20 idle%-88.53
798300 MSSQLServer tpm
CPU all usr%-8.60 sys%-1.15 irq%-0.21 idle%-90.32
633126 MSSQLServer tpm
Vuser 1:1 ...,
CPU all usr%-9.63 sys%-1.14 irq%-0.20 idle%-89.01
709704 MSSQLServer tpm
CPU all usr%-9.96 sys%-1.36 irq%-0.23 idle%-88.48
715080 MSSQLServer tpm
CPU all usr%-9.32 sys%-1.37 irq%-0.25 idle%-88.89
696954 MSSQLServer tpm
CPU all usr%-9.82 sys%-1.37 irq%-0.21 idle%-88.90
693246 MSSQLServer tpm
CPU all usr%-10.60 sys%-1.24 irq%-0.28 idle%-88.34
787812 MSSQLServer tpm
CPU all usr%-10.14 sys%-1.62 irq%-0.21 idle%-88.12
705366 MSSQLServer tpm
Vuser 1:2 ...,
CPU all usr%-9.94 sys%-1.30 irq%-0.22 idle%-88.89
724170 MSSQLServer tpm
CPU all usr%-9.21 sys%-1.15 irq%-0.12 idle%-89.04
687822 MSSQLServer tpm
CPU all usr%-9.28 sys%-1.21 irq%-0.19 idle%-89.94
701604 MSSQLServer tpm
CPU all usr%-9.03 sys%-1.15 irq%-0.19 idle%-89.85
709374 MSSQLServer tpm
CPU all usr%-11.77 sys%-1.80 irq%-0.24 idle%-85.23
743028 MSSQLServer tpm
CPU all usr%-9.99 sys%-1.45 irq%-0.18 idle%-89.20
706362 MSSQLServer tpm
Vuser 1:3 ...,
Vuser 1:Test complete, Taking end Transaction Count.
Vuser 1:4 Active Virtual Users configured
Vuser 1:TEST RESULT : System achieved 306939 NOPM from 713241 SQL Server TPM
Vuser 1:FINISHED SUCCESS
Vuser 3:FINISHED SUCCESS
Vuser 5:FINISHED SUCCESS
Vuser 2:FINISHED SUCCESS
Vuser 4:FINISHED SUCCESS
ALL VIRTUAL USERS COMPLETE
Benchmark Run jobid=67FD2A43565C03E223637343

The transaction counter can be stopped with tcstop.

hammerdb>tcstop
Transaction Counter thread running with threadid:tid0000000000003198
Stopping Transaction Counter

and metrics with metstop.

hammerdb>metstop
Stopping Metrics Agent and Display on raven:27768