On Thu, 18 Aug 2011 09:29:45 -0400, "Dave Richards" <drichard(a)largo.com>
Good morning all,
I work for the City of Largo, Florida and we are trying to get
the last push to go live with an OpenSuse 11.4 server and the GNOME
desktop. Unfortunately we seem to have a low level problem that is
keeping that from happening. I mentioned some of it on a recent blog
The server seems to have some kind of scheduling problem and acts like a
machine that is swapping, yet nothing is showing up on top and we appear
to have plenty of memory. Even local disk access is slow, and the
networking layer is showing lots of packets being lost.
When I have about 10 users on, the machine is very fast and works as
expected. When I get to about 40, it has a huge slowdown and runs
poorly. With 40 users on, when I "vi /etc/hosts" it sits and blinks for
3 seconds before the file appears. Navigation is sluggish.
An older server with older OpenSuse can run 200 users easily with no
The blog comments had a few tips, which I have tried with no changes in
performance. It just really feels like a low level bug/problem that is
not fixable by me by settings or tuning. Top shows plenty of CPU and
If anyone wants to email me with tips or chat with me on the IRC, I'm
logged in as dave_largo.
I noticed that some newer kernels (3.0.1) are in the experimental
channels, if that will resolve my issues I can certainly try and
Current kernel is:
Thanks in advance, right now I'm completely at a road block.
Disclaimer: According to Florida Public Records Law, email
correspondence to and from the City of Largo, including email addresses
and other personal information, is public record and must be made
available to the public and media upon request, unless otherwise exempt
by the Public Records Law.
Perhaps install and run iotop and see what disk I/O is doing another
program which may assist is gkrellm 
iotop watches I/O usage information output by the Linux kernel
(requires 2.6.20 or later) and displays a table of current I/O usage by
processes or threads on the system. At least the
CONFIG_TASK_DELAY_ACCT, CONFIG_TASK_IO_ACCOUNTING, CONFIG_TASKSTATS and
FIG_VM_EVENT_COUNTERS options need to be enabled in your Linux
kernel build configuration.
iotop displays columns for the I/O bandwidth read and written
by each process/thread during the sampling period. It also displays the
percentage of time the thread/process spent while swapping in and
while waiting on I/O. For each process, its I/O priority (class/level)
is shown. In addition, the total I/O bandwidth read and written
during the sampling period is displayed at the top of the interface.
Use the left and right arrows to change the sorting, r to
reverse the sorting order, o to toggle the --only option, p to toggle the
--processes option, a to toggle the --accumulated option, q to quit
or i to change the priority of a thread or a process' thread(s). Any
other key will force a refresh.
 from gkrellm-2.3.5-6.3
With a single process, gkrellm manages multiple stacked monitors
and supports applying themes to match the monitors appearance to your
window manager, Gtk, or any other
· SMP CPU, Disk, Proc, and active net interface monitors with
· Internet monitor that displays current and charts historical
· Memory and swap space usage meters and a system uptime
· File system meters show capacity/free space and can
· A mbox/maildir/MH/POP3/IMAP mail monitor which can launch a
mail reader or remote mail fetch program.
· Clock/calendar and hostname display.
· Laptop Battery monitor.
· CPU/motherboard temperature/fan/voltages display with
warnings and alarms. Linux requires a sensor configured sysfs, lm_sensors
modules or a running mbmon daemon.
FreeBSD can also read the mbmon daemon. Windows requires MBM.
· Disk temperatures if there's a running hddtemp daemon.
· Multiple monitors managed by a single process to reduce system
· A timer button that can execute PPP or ISDN logon/logoff
· Charts are autoscaling with configurable grid line resolution,
· can be set to a fixed scale mode.
· Separate colors for "in" and "out" data. The in color is
for CPU user time, disk read, forks, and net receive data. The out color
is used for CPU sys time, disk
write, load, and net transmit data.
· Commands can be configured to run when monitor labels are
· Data can be collected from a gkrellmd server running on a
· gkrellm is plugin capable so special interest monitors can be
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org