|
When I first
started testing Zenoss I had it on a 64-bit VM with 1GB of memory.
After putting just a handful of devices in monitoring, the web UI was
definitely sluggish, memory usage was through the roof, and the swap
was getting slammed. Now the machine has 2GB of memory, and the output
of `free -m` looks like this: total used free shared buffers cached Mem: 2048 1898 149 0 344 391 For reference, I'm currently only monitoring 42 devices in a test environment. I don't know how Zope manages memory, but I know that Linux caches very aggressively. For example, our neteng department uses zenoss to manage about 850 devices (50k data points). They have 8GB of RAM in their server, and Linux is using 6GB of that in cache. Anyway, the point is that a lot of what you're seeing is Linux's memory management at work. seth wright ([EMAIL PROTECTED]) windows engineer 540.568.2912 (office) james madison university kpascoe wrote: Sorry, I should have given a little more info on the system.It's a standard 32bit P4 with 1GB of memory. I'm running zenoss on the latest stable Debian release (Etch). I'm monitoring 89 devices registered in zenoss, with around 50 of those being monitored via snmp and the others having the snmp monitoring turned off as I just need ping results from them. I also have the DrawMapLinks zproperty set to false in locations. -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=12253#12253 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users |
_______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
