-
Notifications
You must be signed in to change notification settings - Fork 251
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
cant delay first iteration #84
Comments
I hit the same problem. However, as a stop gap arrangement - I skip the first couple of readings (i poll every 2 seconds) before starting to log the CPU. I am sure it's easy to work out how ;-) Hope this helps. |
yeah, but I'm sending this data to splunk so you can see the issue here. |
Haven't really worked with splunk, so any more information would be useful in making suggestions. My use-case was that I generated a CSV from jvmtop runs that was used as a data source. |
As a rough guess, the initial higher cpu usage might be caused by the attach mechanism itself. Additionally, the remote jvm needs to load additional classes (and may JIT them afterwards) beforehand for the communication with jvmtop. All of this does cost cpu time, of course. That's why I suspect the higher indicated cpu time within the first seconds after attaching to be correct (and you're free to skip those readings, as mskadu suggested). |
Yes, that's what I have decided. I have updated jvmtop.sh to my requirements.
|
From the jvmtop usage, I can see delay can be set between the iterations but I can not have the delay set for the first iteration itself. The reason I'm asking for this is when I run the jvmtop.sh for the first time, it shows higher values of %cpu for jvmtop as well as other jvms running. I wanted to have the correct %cpu after certain time lets say 5 sec.
The text was updated successfully, but these errors were encountered: