Given that it is very hard to really test your application's response time on a computer, without using the actual target machine with the real end users signed on and using the system (which is a rather late stage to do such a test), you might find that it is better to apply a "paper estimation" to your critical transactions.
You could base such a test on the following calculation tables, which produce an "ERUF" (Estimated Resource Utilization Factor) for all, or parts of, individual transactions.
An ERUF indicates the type of relative response time you could expect, given the amount work that your function does.
Before attempting to use these ERUF calculation tables, you should be aware of the following:
The Recommended ERUF Ranges are for BUSY Production Machines
ERUF Values are NOT Response Times
Associating ERUF Values With Response Times is a MAJOR Mistake
ERUF Values for Batch Transactions do NOT indicate Elapsed Time
Realistic Estimates are Important
A High ERUF Value Does Not Mean That Your Transaction Is Invalid
