You can refer columns for 80th, 90th or 95th percentile (As per Rational Performance Testing convention). This is again requirement from client. If it is required from client that operations for 95% users should get completed in 8 sec. then you have consider this column.
A highly advanced bug is indistinguishable from a feature.
Why not create a seperate marking transaction for response times over eight seconds on length? Before you end the transaction, use lr_get_transaction_duration() and lr_get_transaction_status() to collect the time and the status of the transaction. If the status is LR_PASS and the transaction duration is greater than eight seconds, use lr_set_transaction() to create a separate marking/tracking transaction for those items which are soft failures....that is the transactions complete, but not within the allotted SLA interval.
In your reports at the end you will be very easily able to compare your soft failures to your total number of passes. Soft failures represent your SLA violations. Pull a ratio from the total number of passed soft-failures to the total number of passes and you have your SLA violation rate.
Now if you're the six sigma type it's time to pull out your sliderule and copy of SAS/SPSS and find out which sigma level your number of SLA violations corresponds to.
For even more interesting use, take your soft errors (SLA violations), multiple that figure by your hard errors for a given transaction. Sort decending by this product and "viola," you have a ranked engineering priority document for use in direting your efforts to address the most offensive transactions.
Food for thought,
[ 02-11-2004, 09:50 AM: Message edited by: James Pulley ]