LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

RE: CPU Spike every 10 hours

To: "'lvs-users@xxxxxxxxxxxxxxxxxxxxxx'" <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: RE: CPU Spike every 10 hours
From: "Radomski, Mike" <Mike.Radomski@xxxxxxxxxxxxxxxxxx>
Date: Thu, 14 Mar 2002 06:44:31 -0500

I have an update to the problem.  It has been over 10 hours since the last sustained spike.  I remember when setting up the heartbeat, the serial connection was very slow and intermittent. If I cat'ed information to the serial port, it would take about 30 seconds to reach the other end of the null modem cable.  As per a suggestion on Google Groups, I tried to set the serial port with the following:

/bin/setserial /dev/ttyS1 irq 0

This worked both with simple serial communication and heartbeat.  But I found in the dmesg and the logs the following:

ttyS: 2 input overrun(s)
ttyS: 2 input overrun(s)

After shutting off the serial heartbeat, the over all load dropped about .02.  I have not seen the sustained spike since.

Does anyone have any suggestions on the serial connection problem?

Mike Radomski
 
SUNY - ITEC
Information Technology Exchange Center
Systems Programmer/Analyst
E-mail: Mike.Radomski@xxxxxxxxxxxxxxxxxx
Systems E-Mail: scsys@xxxxxxxxxxxxxxxxxx        
Phone: (716)878-4832
Cellular: (716)866-7039
Fax: (716)878-4235
 

-----Original Message-----
From: Lars Marowsky-Bree [mailto:lmb@xxxxxxx]
Sent: Wednesday, March 13, 2002 3:02 PM
To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: CPU Spike every 10 hours

On 2002-03-13T12:52:35,
   "Radomski, Mike" <Mike.Radomski@xxxxxxxxxxxxxxxxxx> said:

> It is now doing it on my primary system.  Here is the top output.

OK. It is something in the kernel, because that is the only thing which is not
accounted for by anything else.

There are other options; if you boot the kernel with the "profile="" you can
use readprofile to compare the patterns for 5 minutes during the events and
outside; remember to use "readprofile -r" to reset the profiling data when
doing so so the counters are clean and do NOT run top during the time, because
top traverses the /proc file system every second or so which greatly obscures
the profiling results.

Sincerely,
    Lars Marowsky-Brée <lmb@xxxxxxx>

--
Perfection is our goal, excellence will be tolerated. -- J. Yahl


_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://www.in-addr.de/mailman/listinfo/lvs-users

<Prev in Thread] Current Thread [Next in Thread>