NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Yessir, (or should I say Yes,sar), that sounds like a good idea. I may sound hopelessly simpleminded, but I've never figured out a good way to really interpret what I see in a typical top output. Often times, even if I list the loads on each individual CPU, they sum up to nowhere near what the total CPU load I see with "uptime", "w", or the "top" of "top". Any suggestions would be welcome. _____________________________________________ Kevin Tyle, Systems Administrator Dept. of Atmospheric & Environmental Sciences University at Albany Earth Science 235, 1400 Washington Avenue Albany, NY 12222 Email: ktyle@xxxxxxxxxx Phone: 518-442-4578 _____________________________________________ -----Original Message----- From: daryl herzmann [mailto:akrherz@xxxxxxxxxxx] Sent: Wednesday, October 23, 2013 2:01 PM To: Tyle, Kevin R Cc: awips2-users@xxxxxxxxxxxxxxxx Subject: Re: [awips2-users] CPU load on EDEX/LDM server Kevin, It would be good to interogate system monitoring tools like 'sar' to see what it is logging for CPU vs IO wait percentages. In general, high CPU load is typically tied to processes / threads waiting for IO to occur. If your disk is unable to keep up with raw IO or intensive metadata operations, that could be the trouble. Running 'top' will also show you if your processes are chewing actual CPU or the load average is artificially high with IO wait being to blame. daryl On Wed, 23 Oct 2013, Tyle, Kevin R wrote: > A follow-up: the high CPU load was almost certainly linked to the ldm server > that was running. Once it was shut down, load dropped to close to 0. Upon > restart, load jumped back up to the vicinity of 20.00. I then shut down the > LDM and purged the data directories (which were very very large since no > scouring had been done). Restarting the LDM shows low system load so far. I > will enable LDM scouring and keep an eye on things. > > _____________________________________________ > Kevin Tyle, Systems Administrator > Dept. of Atmospheric & Environmental Sciences University at Albany > Earth Science 235, 1400 Washington Avenue Albany, NY 12222 > Email: ktyle@xxxxxxxxxx<mailto:ktyle@xxxxxxxxxx> > Phone: 518-442-4578 > _____________________________________________ > > From: awips2-users-bounces@xxxxxxxxxxxxxxxx > [mailto:awips2-users-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Tyle, > Kevin R > Sent: Tuesday, October 22, 2013 11:00 AM > To: awips2-users@xxxxxxxxxxxxxxxx > Subject: [awips2-users] CPU load on EDEX/LDM server > > Hi, > > I am running an EDEX server, also running LDM, using the 13.2 version > that Michael has made available to us. It is on a CentOS5 platform, > 32-bit, 16 CPU, 12 GB RAM. I am not running CAVE on this machine. > > I regularly see an average load around 20.00, which seems excessive. > Lots of java, httpd, postmaster processes owned by user awips. > > Does this load seem excessive? What do others see? If this load indeed > seems excessive, any ideas to troubleshoot? > > Thanks, > > Kevin > > _____________________________________________ > Kevin Tyle, Systems Administrator > Dept. of Atmospheric & Environmental Sciences University at Albany > Earth Science 235, 1400 Washington Avenue Albany, NY 12222 > Email: ktyle@xxxxxxxxxx<mailto:ktyle@xxxxxxxxxx> > Phone: 518-442-4578 > _____________________________________________ > > -- /** * Daryl Herzmann * Assistant Scientist -- Iowa Environmental Mesonet * http://mesonet.agron.iastate.edu */
awips2-users archives: