QPID-4030: report failure to meet desired send rate in latencytest tool
Review Request #5299 - Created May 30, 2012 and submitted
The inability to actually meet the desired send rate in qpid-latency-test is not communicated directly. This is particularly obfuscating when used in conjunction with the --sync option which prevents backlog and ever increasing latencies which would normally indicate problems.
Some ad hoc testing above and below achievable rates to verify basic approach works ok. I check every 100,000 which is a little arbitrary but works reasonably for me in practice.
Posted (June 1, 2012, 1:22 p.m.)
How would you feel about throwing an exception if the rate cannot be held? Or perhaps having the tool return a well defined error code in that case? I'm thinking about the scripting case - we may want to detect this failure programmatically. Not a requirement - just pondering....
Review request changed
Updated (June 18, 2012, 3:20 p.m.)
- changed from pending to submitted