Manually stoping coverband about coverband HOT 4 CLOSED

interesting idea, and we could implement something to help with this... I will note, the way Ruby's coverage works you can't start after the server is running you need to do it as it does code loading when the server is booting... You can stop collecting but most of the instrumentation hooks still run, so it wouldn't do much in terms of reducing performance overhead or anything like that.

So with that in mind what are you trying to achieve or why would you want not have it running all the time? If you are concerned with overhead, setting a stop ENV var and restarting the servers is the best way to ensure no overhead impacts performance.

from coverband.

Yes, I'm concerned about the overhead. I thought being able to start it manually and collect metrics for an hour or so and then stop it to have a look at the metrics.

I understand now what you mean. You mention the stop ENV is this something that coverband already provides?

from coverband.

yeah, correct... so you would do a configuration change of the environment to toggle the measuring on and off... This is because the performance impact even if you stop collection still exists as the code is instrumented when loaded...

so the workflow for this would be:

1. deploy with the env var COVERBAND_DISABLE_AUTO_START=true for no coverband no performance impact
2. deploy with the env var COVERBAND_DISABLE_AUTO_START removed entirely, to turn on coverband
3. deploy with the env var COVERBAND_DISABLE_AUTO_START=true to turn back off coverband ensuring no performance impact

from coverband.

Great will try that! Thanks a lot!

from coverband.