Re: Performance problems

Bill WIlson <[email protected]>
Newsgroups gmane.comp.gnome.apps.gkrellm
Message-ID <[email protected]>
On Tue, 03 Jul 2007 13:45:55 -0700
Rob Brandt <[email protected]> wrote:

> I have a number of gkrellm monitors watching different servers.  All the 
> servers are linux, the clients are running on Windows XP SP2.
> 
> Three of them are running fine, but one of them is a continual problem:
> 
> * the http monitor works correctly for a while, but soon stops 
> discarding old connections.  At this moment, is says there are 3221 http 
> connections, and that number will never go down.
> 
> * smtp has the same problem.
> 
> * it will eventually consume substantial CPU resources.  My other 
> monitors typically run at around 3% processor utilization, and the 
> problem one is running at that level now.  However, at some point I will 
> notice my entire PC lagging, will check utilization and this monitor 
> will be consuming from 40-50% of the processor.
> 
> * It will eventually "freeze"; actually, I think it's still alive but 
> crawling so slow that it appears to be non-functional.
> 
> The parameters for this monitor are the same as the others except for 
> the IP address of the server.

If you quit and restart the problem gkrellm, does it start back up showing reasonable
values?   And could you try monitoring that server with a gkrellm on a Linux box to
see if it's that the server stops sending the disconnect data or if it's a problem with
the Windows client gkrellm.   If you were running a Linux gkrellm client I would
suggest collecting debug internet connection data by running:

    $ gkrellm -s server -d 0x1000 | grep "^+0\|^<inet>\|-0" > logfile

but I don't know if you can do something like this on your Windows box.

Bill
_______________________________________________
Gkrellm mailing list
[email protected]
http://lists.jutley.org/cgi-bin/mailman/listinfo/gkrellm
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.