• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Yellow Bricks

by Duncan Epping

  • Home
  • ESXTOP
  • Stickers/Shirts
  • Privacy Policy
  • About
  • Show Search
Hide Search

esxtop running out of control?

Duncan Epping · Jun 1, 2010 ·

One of my colleagues (Thanks Horst) pointed me to this option I had never noticed with ESXTOP “-l”. The option has been added to avoid high CPU utilization as the result of a large amount of LUNs during collection of the storage statistics.

kb 1005894
Add a lock mode (-l) to esxtop to help optimize CPU utilization.

In a large ESX Server deployment that includes many LUNs, esxtop usesa lot of CPU while accessing storage statistics.

To alleviate this problem, you can use the -l option with esxtop to enable lock mode. This option locks the entities (worlds, virtual CPUs, LUNs, NICs, and so on) for which statistics are displayed. Any new entities created during the esxtop session will not have statitistics displayed.

Batch mode (-b) also implies lock mode.

Related

Server, Various esxtop, performance

Reader Interactions

Comments

  1. Alvin Rheaves says

    23 June, 2012 at 18:07

    Keep functioning, remarkable job!

Primary Sidebar

About the author

Duncan Epping is a Chief Technologist in the Office of CTO of the Cloud Platform BU at VMware. He is a VCDX (# 007), the author of the "vSAN Deep Dive", the “vSphere Clustering Technical Deep Dive” series, and the host of the "Unexplored Territory" podcast.

Upcoming Events

May 24th – VMUG Poland
June 1st – VMUG Belgium
Aug 21st – VMware Explore
Sep 20th – VMUG DK
Nov 6th – VMware Explore
Dec 7th – Swiss German VMUG

Recommended Reads

Sponsors

Want to support Yellow-Bricks? Buy an advert!

Advertisements

Copyright Yellow-Bricks.com © 2023 · Log in