MySQL OLTP (Transactional) - Hammerora - SourceForge

More documents

Recommendations

Info

Figure 48 Timed Test Driver Options Once the Timed Test Driver Script is selected this activates the options to select the Minutes of Rampup Time and Minutes for Test Duration as described previously in this guide. For a performance profile test you should plan to keep the Minutes of Rampup Time and the Minutes for Test Duration consistent for a number of tests with an increasing number of Virtual Users. For this reason you should plan to allocate sufficient rampup time for the higher number of Virtual Users at the end of your test sequence as well as the smaller number at the start. When you have selected your options click OK. From under the Benchmark and TPC-C Menu select TPC-C Driver Script, this populates the Script Editor Window as shown in Figure 49 with the Timed Test Driver Script configured with your chosen options.
Figure 49 AWR Snapshot Driver Script To change these options you can either change them in the Schema Options window and reload the driver script or more advanced users can also change them directly in the Driver Script itself. To run the Timed Test Driver Script you must configure the Virtual Users as you did with the Standard Driver Script however there are two notable differences to observe. Firstly when running the Timed Test Driver Script one Virtual user will not run the Driver Script workload, instead this one Virtual User will monitor the timing of the test, measure the average transaction values and return the results. For this reason you should configure your Virtual Users with a Virtual User + 1 approach. ie to measure the workload for 1 Virtual User you should configure 2 Virtual Users, to measure the workload for 2 virtual Users you should configure 3 and so on. Additionally the Timed Test Driver Script is designed to be run with the Virtual User output enabled in order that you can view the Output from the Virtual User doing the monitoring, consequently the output for the Virtual Users running the workload is suppressed. The Virtual User configuration for the first test will look as Figure 50.
Page 1 and 2: MySQL OLTP (Transactional) Load Tes
Page 3 and 4: esults. It is important to emphasis
Page 5 and 6: Figure 3 Performance Profile Exampl
Page 7 and 8: the storage required. Hammerora con
Page 9 and 10: Figure 5 Windows Environment Variab
Page 11 and 12: Figure 8 Welcome Choose the destina
Page 13 and 14: Hammerora will be installed in your
Page 15 and 16: Figure 13 Hammerora Hammerora is no
Page 17 and 18: When choosing a MySQL Server to tes
Page 19 and 20: MySQL Database The MySQL Database i
Page 21 and 22: Figure 17 Create Schema On clicking
Page 23 and 24: Figure 20 Schema Build Complete Pre
Page 25 and 26: | Tables_in_tpcc | +---------------
Page 27 and 28: Driver Options Under the Driver Opt
Page 29 and 30: occasional errors being reported as
Page 31 and 32: Pre-Test 1 Verifying the Schema Fig
Page 33 and 34: Figure 29 Create Virtual Users You
Page 35 and 36: Figure 31 Run Hammerora Load Test Y
Page 37 and 38: Figure 33 Virtual Users Complete If
Page 39 and 40: Figure 35 One Virtual User Note tha
Page 41 and 42: Transaction Counter Options Under t
Page 43 and 44: Figure 41Waiting for Data After the
Page 45 and 46: Figure 44 Running Multiple Virtual
Page 47: maximum throughput, measuring trans
Page 51 and 52: database. You can check how this is
Page 53 and 54: Figure 55 Autopilot Options shown i
Page 55 and 56: Figure 57 Autopilot Screen The Auto
Page 57 and 58: Figure 59 Autopilot Complete The Ha
Page 59 and 60: When you have data for multiple sys

MySQL OLTP (Transactional) - Hammerora - SourceForge

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?