DayTrader Scenario Runtime Statistics DayTrader
Trade Reset completed successfully Modify runtime configuration
Benchmark scenario statistics
Benchmark runtime configuration summary Value
Run-Time Mode Full EJB3
Order-Processing Mode Sync
Web Interface JSP
Active Traders / Trade User population 0 / 15000
Active Stocks / Trade Stock population 10000 / 0
Benchmark scenario verification
Run Statistic Scenario verification test Expected Value Actual Value Pass/Fail
Active Stocks Active stocks should generally equal the db population of stocks 0 10000 Warn
Active Traders Active traders should generally equal the db population of traders 0 15000 Warn
Estimated total requests Actual benchmark scenario requests should be within +/- 2% of the estimated number of requests in the last benchmark run to pass. 3.0 see2 see2
New Users Registered 2.0% of expected requests (0.02 * 3.0 ) 0.06 0 N/A
Logins 4.0% of expected requests (0.04 * 3.0 ) + initial login 0.12 0 N/A
Logouts #logouts must be >= #logins-active traders ( 0 - 15000 ) -15000 0 Pass
User Holdings Trade users own an average of 5 holdings, 5* total Users = ( 5 * 0) 0 0 N/A
Buy Order Count 4.0% of expected requests (0.04 * 3.0 ) + current holdings count 0.12 0 N/A
Sell Order Count 4.0% of expected requests (0.04 * 3.0 ) 0.12 0 N/A
Total Order Count 8.0% of expected requests (0.08 * 3.0 ) + current holdings count 0.24 0 N/A
Open Orders All orders should be completed before reset3 0 0 Pass
Cancelled Orders Orders are cancelled if an error is encountered during order processing. 0 0 Pass
Orders remaining after reset After Trade reset, each user should carry an average of 5 orders in the database. 5* total Users = (5 * 0) 0 0 N/A
  1. Benchmark verification tests require a Trade Reset between each benchmark run.
  2. The expected value of benchmark requests is computed based on the the count from the Web application since the last Trade reset.The actual value of benchmark request requires user verification and may be incorrect for a cluster.
  3. Orders are processed asynchronously in Trade. Therefore, processing may continue beyond the end of a benchmark run. Trade Reset should not be invoked until processing is completed.
  4. Actual values must be within 5% of corresponding estimated values to pass verification.
DayTrader Scenario Runtime Statistics DayTrader