[Cialug] Server Monitoring/Management

[Matthew Nuzum]

On Jan 29, 2008 7:27 PM, Colin Burnett <cmlburnett at gmail.com> wrote:

> On Jan 29, 2008 6:20 PM, Chris K. <lister at kulish.com> wrote:
> > Colin,
> >
> > My primary basis for that statement was a dual 1G P3 server with 512M of
> > RAM and 1024M of swap monitoring 2 physical devices (about 10-12
> > services).  The poor thing began swap usage in about 15 minutes and had
> > finally used everything (physical + swap) in about 8 hours.
> >
> > Keep in mind the Zenoss instances and MySQL DB were on the same server.
>
> That said, if it churns through 1/2 G in 15 minutes then it's
> horribly, horribly, horribly bloated for **what little I think it's
> doing** (Wirth's law) or its got an insane memory leak.  (By insane I
> mean never-ever frees memory.  Ever.)  So I am thoroughly confused how
> "pinging" 2 machines and "opening sockets" to a dozen ports requires
> that much CPU time AND that much memory.
>
> I was hoping for more of an explanation about what would take up a gig
> of ram to monitor services.


Maybe the resources are needed to ensure low latency (i.e. keeping the
working data set and application entirely in ram and disk cache).
-- 
Matthew Nuzum
newz2000 on freenode
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://cialug.org/pipermail/cialug/attachments/20080129/56556dfe/attachment.htm