On Tue, 01 Jul 2014 14:47:19 +0200 Sigurd Mytting sigurd@mytting.no wrote:
| Our current template for customer deployments is a single Intel Xeon | E5620 (Quad core @ 2.40GHz) based server, with 12GB RAM and 4x600GB 10K | SAS disks in a RAID 10 configuration.
Out of curiosity, how many devices/port would run fairly ok on such a configuration?
Biggest I see is 519 devices / 17701 ports, but this server stopped breathing ok after the upgrade to NAV 4 and Graphite.
We also have one with 194 devices / 19308 ports. This one is a bit high, but not enough to alarm us in any way.
The port count will drive up the load for storing statistics, while the device count will drive up the general load for monitoring.
| If your existing server is running fine with both NAV 3.15 and | PostgreSQL, I probably wouldn't deviate from that, but you might want to | start thinking about a separate Graphite server with SSDs for NAV 4.0.
'Running fine' is a matter of definition, my current setup works, but it could be a lot more snappy. From your input I guess I'll go for three servers, putting postgres and graphite on dedicated iron.
You will have a lot more leeway for scaling up with that configuration, at least :-)
Would graphite hogg memory? I have a couple of server with 96GB and one with 32GB ram available, should I put memory on graphite?
I'd say the memory footprint of Graphite is negligible. The carbon-cache daemons will cache datapoints in memory to smooth out I/O-write activity, but you generally don't want them to keep a lot of uncommitted data around in memory.
The graphite-web component will use a little bit more memory, but we're still talking sub-gigabyte levels. Once your start graphing a lot, it makes sense to throw a small memcache instance on it to improve performance, but still, I'd say 32GB is way overkill :) If you're not afraid of a little data loss, you could use that to store all your Whisper files in a ramdisk and sync them to physical, rotating drives every so often ;-)