Database Reference
In-Depth Information
as you might guess, the total number of purchases during a given run. For our run, the
value returned was
n_purchase_overall=461871
, meaning we has 461,871
purchases go through our system.
How about login experience? The next value,
rt_login_avg_msec
, provides us
with the average login time in milliseconds for a user. For our run, we received a
rt_login_avg_msec=4
, meaning our users' login time for the system, on average,
was 4 milliseconds.
What about new user experience? The
rt_newcust_avg_msec
metric tells us how
long it takes for a new user to register themselves with our service. For our test, the
value we received was
rt_newcust_avg_msec=2
, meaning a new user
registration took 2 milliseconds.
How about the browse time? Metric
rt_browse_avg_msec
represents browse
time. For our run, the value returned was
rt_browse_avg_msec=0
.
The average purchase time is represented in the
rt_purchase_avg_msec
value.
For our run, we received a result of
rt_purchase_avg_msec=8
, meaning it took
an average of 8 milliseconds for a purchase to complete.
What happens if a customer is trying to order something but there is not enough of that
product in stock and the order needs to roll back? This is represented as a total number
experienced during the entire run in the
n_rollbacks_overall
value. For our run,
we received a value of
n_rollbacks_overall=9361
, meaning we had 9,361
orders rolled back due to a lack of product.
The value
rollback_rate
represents the percentage of rollbacks and is derived by
the following formula, as described in ds2driver_doc.txt
:
n_rollback_overall / n_overall * 100%
For our test, we received a value of
rollback_rate = 2.0%
, meaning we had
2.0% of our orders rolled back. The math is 9361/461871*100%.
How stressed was the vCPU of our host? The
host <servername> CPU%
will
provide this information. The result we received for our run was
host
sql2012a.s2012dir.domain CPU%= 8.5
, which states our sql2012a virtual
machine ran at about 8.5% CPU utilization, so we barely touched the system from a
CPU perspective.
The final two values are
n_purchase_from_start
and
n_rollbacks_from_start
, which represent the total number of purchases and
rollbacks from the start of the test, including warm-up time, through exiting of the
thread(s). For our test, these values are represented as
n_purchase_from_start=
464940
and
n_rollbacks_from_start= 9422
, respectively.
