The information in this post is a duplicate of this GitHub Issue https:\/\/github.com\/TPC-Council\/HammerDB\/issues\/84. The issue regards running build and driver scripts automatically in Windows.\u00a0 As both build and driver examples are not given together in previous posts, the examples are copied here. This is intended as a template that you can take and modify for your own needs.<\/p>\n
A few things to note. Firstly these scripts are multithreaded so once you do build schema and vurun it is running multiple threads. We need a different approach for both because in the schema build we are waiting for all of the virtual users to finish (vwait forever), however for the driver we are waiting for a set period of time before terminating them. For the build I have created more warehouses but with 5 virtual users to show the multithreaded nature of the build. For the driver we have set a rampup and duration of 3 minutes in total (180 secs) – this runs in the virtual users, then in the main monitor virtual user it runs a timer – this is set to 200 seconds more than the rampup and driver combined (if it is less it will terminate the test before ending).<\/p>\n
With both I copied the scripts to C:\\Program Files\\HammerDB-3.3. I then did:<\/p>\n
and<\/p>\n When both are complete the shell will exit as intended therefore it is a good idea to set logtotemp to ensure that you receive both the output and errors (for example if the build script exits because the database already exists).<\/p>\n Build Script – autorunbuild.tcl<\/p>\n Driver Script – autorundrive.tcl<\/p>\n A recommended editor that recognises TCL syntax for editing HammerDB script is Vim.\u00a0<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" The information in this post is a duplicate of this GitHub Issue https:\/\/github.com\/TPC-Council\/HammerDB\/issues\/84. The issue regards running build and driver scripts automatically in Windows.\u00a0 As both build and driver examples are not given together in previous posts, the examples are copied here. This is intended as a template that you can take and modify for … <\/p>\nhammerdbcli.bat auto autorunbuild.tcl<\/code><\/p>\nhammerdbcli.bat auto autorundrive.tcl<\/code><\/p>\nputs \"SETTING CONFIGURATION\"\nglobal complete\nproc wait_to_complete {} {\nglobal complete\nset complete [vucomplete]\nif {!$complete} { after 5000 wait_to_complete } else { exit }\n}\nputs \"SETTING CONFIGURATION\"\ndbset db mssqls\ndiset connection mssqls_server {(local)\\SQLDEVELOP}\ndiset tpcc mssqls_count_ware 10\ndiset tpcc mssqls_num_vu 5\nvuset logtotemp 1\nbuildschema\nwait_to_complete\nvwait forever\n<\/code><\/pre>\n#!\/bin\/tclsh\nproc runtimer { seconds } {\nset x 0\nset timerstop 0\nwhile {!$timerstop} {\nincr x\nafter 1000\n if { ![ expr {$x % 60} ] } {\n set y [ expr $x \/ 60 ]\n puts \"Timer: $y minutes elapsed\"\n }\nupdate\nif { [ vucomplete ] || $x eq $seconds } { set timerstop 1 }\n }\nreturn\n}\nputs \"SETTING CONFIGURATION\"\ndbset db mssqls\ndiset connection mssqls_server {(local)\\SQLDEVELOP}\ndiset tpcc mssqls_driver timed\ndiset tpcc mssqls_rampup 1\ndiset tpcc mssqls_duration 2\nvuset logtotemp 1\nloadscript\nputs \"SEQUENCE STARTED\"\nforeach z { 1 2 4 } {\nputs \"$z VU TEST\"\nvuset vu $z\nvucreate\nvurun\n#Runtimer in seconds must exceed rampup + duration\nruntimer 200\nvudestroy\nafter 5000\n}\nputs \"TEST SEQUENCE COMPLETE\"\n<\/code><\/pre>\n