multiple data sources • Complex Pass/Fail criteria • Difficult to extract data - e.g. from async queue-based distributed systems • Running analysis on the load generator to avoid transferring huge files across the network
on a remote load generator • Saving on network traffic and time, or for security reasons • https://github.com/hali/Performance-data-processing/ blob/master/scripts/analyze.R
and in test, to compare • https://github.com/hali/Performance-data-processing/ blob/master/scripts/calculate_concurrency.R • https://github.com/hali/Performance-data-processing/ blob/master/scripts/access-log_concurrency.R • bonus: https://github.com/hali/Performance-data- processing/blob/master/scripts/concurrency_graph.R
point • Remove analysis for logs you don't have • Add analysis of your own logs • https://github.com/hali/Performance-data-processing/ tree/master/Pritcel
are tricky • System 1 creates task, System 2 schedules it, all async • Created time and Scheduled time come as payload • Need to correlate JMeter request time and event times to get processing time Load generator API System 1 System 2 Notification Notification Notification