-
Notifications
You must be signed in to change notification settings - Fork 816
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
why counter is very big? #825
Comments
CPU time in nanoseconds
10140865 nanoseconds = 10.14 milliseconds. The default profiling interval is 10 ms; this means, one CPU sample is generated approximately for every 10 ms of CPU time spent in one thread. The counter value reflects the time spent since the last sample - in your example, it expectedly matches the default profiling interval. |
Thank you,I got it ! |
One more question please: |
In allocation profile, counter is always in bytes. |
ok,thank you! |
Hey.i want to ask a question about the value of cpu counter.
First,what's the meaning of cpu counter?
Second,why the cpu counter is so big?
the command like:
./profiler.sh -e cpu xxx
I use async-profiler v2.8.3 to monitor a simple java program of cpu event,and i got very big counter.
So i add logs in code like follow in perfEvents_linux.cpp:
And i got the log like follows:
"enter PerfEvents::signalHandler,counter:10140865".
I am really confused why the counter is so big when the siginfo is 0.
Any reply is grateful.
The text was updated successfully, but these errors were encountered: