--
© 2018 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043
Email preferences: You received this email because you signed up for the Google Compute Engine Discussion Google Group (gce-discussion@googlegroups.com) to participate in discussions with other members of the Google Compute Engine community and the Google Compute Engine Team.
---
You received this message because you are subscribed to a topic in the Google Groups "gce-discussion" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/gce-discussion/IEBFHW4D8m8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to gce-discussion+unsubscribe@googlegroups.com.
To post to this group, send email to gce-discussion@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gce-discussion/4fab90fb-a1c0-47f2-b875-d919766dc995%40googlegroups.com.
Hello Jacob,
In order to check the CPU utilization, you can use the “ top” command from within your GCE linux instance. Check this thread for multiple core metrics. Also, for stress testing, you may install this third party stress tool and run it for at least two minutes as to have it reflect properly on the graph, here is an example (tip: ssh using a new shell while keeping the top command running in the old shell to monitor the spike of usage) :
sudo stress --cpu 8 --timeout 120
The command should get the CPU utilization near 100% for two minutes. You may verify that using the top command (different shell) and through the graph. While stressing the instance, make sure that the graph is set to 1 hour, as the longer the period the bigger the chance that the graph may average and flatten the result. I hope this helps.
Jacob,
The graph on the main dashboard is displaying the metrics as expected. Both metrics are actually the same but displayed differently. The difference is that on the main dashboard, it is displayed in decimal form. For example: 0.01= 1% and 0.1= 10% .. 1.0= 100%. In your case it may have even reached 2.5 = 250%. This is also expected for instances that allow bursting, a feature that allows the instance for short period of times to use additional physical CPU. I hope this clarifies the confusion.