mchr3k/org.intrace — Issue #19: Feature request: burst-mode network requests
Author: eostermueller
Created: 2012-01-10 14:07:44+00:00
State: open

If InTrace is monitoring a remote application, it seems that a separate
network request is made for every trace event. Is that right? -- I haven't
looked closely enough at the code to see. If that is the case, I don't
think that kind of model will scale when medium-to-large amounts of load is applied.
Perhaps we could consider some kind of burst mode where trace events
collect in a queue and are sent to the GUI every X seconds?
CA Introscope, for instance, has a 15 second delay. I'd be happy with 5, but it should be configurable.

We should do some load testing to measure InTrace overhead.
1) Deploy Java PetStore application
2) Use "http://grinder.sourceforge.net/" to apply some load.
3) Measure
* CPU/RAM consumption on PetStore server.
* Get from "The Grinder" Response time and throughput metrics

Compare results from the above test with and without InTrace with instrumentation.
We should have multiple Load tests with InTrace.
1) instrumenting 50 classes
2) instrumenting 100 classes
3) instrumenting 200 classes
4) instrumenting 400 classes