Hi Bernhard, the key here is where you store the rrd files. If you store them on disk, the update speed will be much lower ... the 22k updates are in memory ...
also, note that for high performance you have to use language bindings for the update as starting rrdupdate for every update is quite costly. the main performance gain for large numbers of rrds (on disk) comes from the fact that more rrd-hotblocks can stay in cache with the 1.3 release which means that you can scale to a larger number of rrd files without the performance dropping. Note, that running at 250 Up/s you get to udate 150k RRDs in a 5 minute interval ... cheers tobi Yesterday Bernard Li wrote: > Hi all: > > In the "Features for RRDtool 1.3" wiki page > http://oss.oetiker.ch/rrdtool-trac/wiki/RRDtool13, it mentioned: > > "My CoreDuo Thinkpad was able to do 12k updates per second (in memory) > with the 1.2 code base. With the 1.3 code base it is able to do 22k > updates per second (in memory)." > > and > > "My 5400 RPM Thinkpad HD continues to run at about 250 RRD updates per > second." > > Is there a standard way of measuring this? Or do you simply time how > long it takes to run n updates? > > Thanks, > > Bernard > > _______________________________________________ > rrd-developers mailing list > rrd-developers@lists.oetiker.ch > https://lists.oetiker.ch/cgi-bin/listinfo/rrd-developers > > -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten http://it.oetiker.ch [EMAIL PROTECTED] ++41 62 213 9902 _______________________________________________ rrd-developers mailing list rrd-developers@lists.oetiker.ch https://lists.oetiker.ch/cgi-bin/listinfo/rrd-developers
