New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Client] Instrumentation : memory optimization #46
Comments
Exception in thread "Thread-4" java.lang.NegativeArraySizeException |
High memory overhead on the target JVM's side as well. (see previous comment). |
Instrumenting a method called often leads to very high memory consumption. In my mind, memory usage should be or nearly be independant from the frequency at which methods are called (see implementation of "InstrumentationSample" but probably more importantly (more surprising) the cardinality of StackTraceElement :
In my case, I was sampling at the default 1sec interval and just instrumented a java method which was called 3 million times. It pretty much killed the JVM (-> filled up approximately 2 GB Memory). Is there a way to optimize this?
The text was updated successfully, but these errors were encountered: