[rrd-users] Re: Frontend for RRDTool, What's your opinion?

[Jason Fesler]

> Of course, there is a need having a scalable frontend and data collector
> (SNMP/custom scripts) without reeventing the wheel. And also code which will be
> a startingpoint with clear and functionable code on which i can rely and use to

Ultimatley I wrote my own that was better suited to my environment than the
other front ends were.  RRD's biggest expense is IO, not CPU, at least when
it comes to data storage.  Graphing is CPU intensive, but we solved that by
only showing graphs when needed, and making the display system flexible (I
have a single iamge showing thing that takes all of its info by URL, and
people just make web pages refering to the url to pull the data they want
displayed..).

I currently update 8700 files once a minute; each file has on average 10 DS's.
I'm doing this on an e450 with 2x 8 drive raid5 configurations.  I probably
should have striped things for IO speed - I use every bit of IO I have but
hardly touch the space.  On average I'm in about 60 %busy on IO, which is
definately taking its toll on the machine interactiveness. That machine runs
a load of about 1.2 if nobody is looking at graphs.  This is on sparc CPU's
- the e450 has 4x400 mhz to play with, so system loads to aroudn 4 don't
really bother me.



--
Unsubscribe mailto:rrd-users-request at list.ee.ethz.ch?subject=unsubscribe
Help        mailto:rrd-users-request at list.ee.ethz.ch?subject=help
Archive     http://www.ee.ethz.ch/~slist/rrd-users
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi