Prevent slowdown in long running DB operations

kford-newrelic commented 1 year ago

Description

Some customers could experience slow downs (due to agent use of CPU/memory) when running large DB queries. The agent is waiting for the full transaction to finalise and whilst waiting the application may be perceived as hanging or slowed down.

Customers have expressed their desire to either:

not having this issue at all (not possible since our agent needs to wait for transaction to finish)
implement some kind of "circuit breaker" that stops instrumentation when transaction size is causing app to slow down

We need to find a solution such that long DB calls don't take that long. (Note: @dhilpipre implemented a custom solution for a customer, that he reviewed with the team...could that be a good starting point to look at?)

Acceptance Criteria

When a customer is using our agent with an application that is "database intensive", the agent will reach a point at which it will reduce the amount of DB instrumentation it applies, to reduce CPU/memory utilization.

Design Consideration/Limitations

N/A

Dependencies

N/A

Additional context

See NR-135145 for additional information

workato-integration[bot] commented 1 year ago

https://issues.newrelic.com/browse/NR-159181

kford-newrelic commented 1 year ago

Bottom of the list; may end up below the cut-line

kford-newrelic commented 8 months ago

https://new-relic.atlassian.net/browse/NR-159181

newrelic / newrelic-java-agent