MySQL OLTP (Transactional) - Hammerora - SourceForge
MySQL OLTP (Transactional) - Hammerora - SourceForge
MySQL OLTP (Transactional) - Hammerora - SourceForge
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Info: UPDATE warehouse SET w_ytd = w_ytd + NAME_CONST('p_h_amount',287.00)<br />
WHERE w_id = NAME_CONST('p_w_<br />
*************************** 3. row ***************************<br />
Id: 23<br />
User: root<br />
Host: test.example.com:53574<br />
db: tpcc<br />
Command: Query<br />
Time: 0<br />
State: statistics<br />
Info: SELECT s_quantity, s_data, s_dist_01, s_dist_02, s_dist_03, s_dist_04,<br />
s_dist_05, s_dist_06, s_dist_<br />
3 rows in set (0.00 sec)<br />
and are running transactions as can be observed in the Virtual User Output as shown in Figure 32.<br />
Figure 32 Load Testing Running<br />
When the Virtual Users have completed all of their designated transactions they will exit showing a positive<br />
status as shown in Figure 33. Once the Virtual User is displaying this positive status it has logged off the<br />
database and will not be seen in V$SESSION. The Virtual User is once again idle and not running<br />
transactions. The Virtual User does not need to be destroyed and recreated to re-run the test from this<br />
status. The Virtual Users can be destroyed to stop a running test.
Change language