Just to add a few details which are missing from the post: the server has a 2.2GHz processor and he is monitoring very close to 600 devices (about 20000 datapoints).  The system is overall underpowered.  I explained to you last night that collecting performance data for that many devices on a single Zenoss collector is very performance intensive and that you need a server which will be able to handle the load.  I also explained that Zenoss always starts off using a small amount of memory and then starts using more and more as it caches stuff.  It will eventually reach a point where it will not consume any more memory (hence this is not a leak).  You simply don't have enough physical memory in that server to accomodate the memory requirements for monitoring almost 600 devices.  2.2GHz is also very low for that level of monitoring.  You need to upgrade the Memory and the CPU for starters.  If you still see performance issues then you would need to get faster disks (a SAN or something).

I have a server running Zenoss 2.4.5 which is monitoring 352 devices and around 18000 datapoints.  I have 6GB of RAM in the server, but the overall memory usage tops out at around 4.5GB after a few weeks (which would explain why you, having only 4GB of RAM are seeing swap usage after Zenoss has been running for a couple of weeks).

Start by adding memory to the server, if you still experience the issue after you upgrade the RAM (which I'll bet that you won't), then post again with your findings.  2.2GHz is not enough to be monitoring that many devices, get a better processor in there as well.

If you continue to have issues after upgrading the RAM be sure to make it known.  If there is in fact some memory leak which we're not aware of it would be good to be able to nail down the cause.

I've been looking in to this.  I recently edited my zope.conf and dropped the zthread setting down from 50 to 4 on one of my servers.  It appears to have not only improved performance but also seems to have had a positive effect on the amount of memory usage.  I'm going to leave it running to see if it eventually creeps in to swap.  Also, you mentioned zenperfsnmp using up a lot of memory, have you checked Zope?  On mine it's Zope that uses up the vast majority of the memory.  Zenperfsnmp comes in second with about 15% usage.

Did you create the CPU and Memory usage graphs yourself?

Ah, I thought they were some default graphs which I was missing or something.  It'd be nice if they'd include graphs like that for each collector by default.

Will do.  I've never created a ZenPack with anything other than perf templates in it, so I don't know how to have it include the script.  Will post them all separately in a Document here shortly.

docs/DOC-4681