Page 1 of 1

Raspberry MRTG limitation

Posted: Wed May 06, 2015 5:41 am
by zeromafia
Hi guys, I really need to know is there limitation on Raspberry when using MRTG compare with normal computer? For example : Limitation to monitor large organization traffic or monitor certain type of traffic.

Re: Raspberry MRTG limitation

Posted: Sun May 10, 2015 1:33 pm
by gdt
You're asking a capacity planning question. So let's talk capacity.

The RPi runs 4 cores at 50-odd MIPS. A modern server will be well north of 4,000 MIPS per core.

The RPi has a disk bandwidth to the SD card of about 10MB/s. A modern disk will be well north of 200MB/s.

Now this only matters if CPU or disk I/O is a bottleneck.

Sadly MRTG is grossly inefficient. It uses a lot of unnecessarily CPU and disk I/O. Large sites struggle to run it even on top-end servers. So a RPi is in no way suitable to run MRTG for a large enterprise (which we'll define as having more than 500 devices to monitor and maybe 20 variables per device).

I suggest you look at a small 1RU server with two large disks set up in a mirrored software RAID configuration.

Then don't run MRTG on it, but more efficient software more tuned to collecting RRDs at a large site: say Torrus, and then using Graphite and Drraw to present the RRDs.

Re: Raspberry MRTG limitation

Posted: Mon May 11, 2015 9:50 am
by amigaholic
I run Cacti on my Pi2 at home (I run a Cisco router, switch, and wireless access point). I use it to tell me things like the ADSL SNR, line attenuation, calculated maximum download/upload speeds, actual bandwidth usage, memory and processor usage. It also tells me how many clients are connected, and to which radio, on my Cisco AP.

Previously I've had Cacti also monitor a laser printer, having it tell me how much toner is left, how much paper is left, how many pages have been printed from it, the number of jobs in the queue, etc. I only don't monitor that now because said printer died.

Cacti uses RRDtool, just like MRTG does. Try using Cacti, and ensure you're polling using the more efficient Spine poller. If you have a Pi2 already, it can't hurt to try setting it up with Cacti and see how many devices it can poll without being able to complete a polling cycle (5 minutes by default, but if you don't need data with 5 minute resolution, you can tell it to poll less frequently).

Cacti can be installed using "apt-get install cacti", and that should cover all the dependencies too, but might install an older version. You can download Cacti from their website - http://www.cacti.net

I'd definitely recommend using a USB hard drive for storing Cacti's data. Save your SD card a lot of writes, and give yourself plenty of capacity.

It's also worth noting that yes, I only have a few devices for Cacti to monitor at home, but that Pi is also a Samba active directory domain controller, a DHCP server, a USB print server, an FTP and TFTP server, a CrashPlan automated backup server, and it also runs Serviio, which is a DLNA streaming media server, and I'm able to stream full-HD Blu-Ray rips from that Pi to my PC or PS3 without stuttering, even when Cacti runs its polls, or when CrashPlan is backing up or compressing old backup archives. The Pi2 has a decent amount of grunt. Give it a shot.