-
Notifications
You must be signed in to change notification settings - Fork 39
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
java-allocation-instrumenter #1
Comments
They are completely different and solve different problems. Java allocation instrumenter is a library that let's you attach your own code to object allocations. Aprof, on the other hand, is a pure-java profiler that is used without any changes in the target code. It gathers detailed allocation statistics (which includes classes and where they are allocated from) with minimal runtime overhead and prints nicely formatted reports. |
That's not entirely true of the Google project. I'm writing something similar to I'm confused why you've re-implemented all the ASM - your approach is identical to theirs - so I am interested to know what extra value your codebase has over theirs. |
The key difference is that "instrumenter" provides generalized facility to attach custom code, but aprof is a ready-to-use profiler with various useful features. |
yes, I understand that... what I don't understand is why you re-wrote the layer that does the instrumentation. Do you feel there is something wrong with the way that the google project are doing it? |
Hi, I was just wondering if you were aware of https://code.google.com/p/java-allocation-instrumenter/ ?
If so, is there anything your aprof does that it doesn't?
The text was updated successfully, but these errors were encountered: