Yeah - look for a private reply - I'll resume the thread when it settles down. -----Burton
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of Kouprie, Robbert > Sent: Tuesday, June 15, 2004 7:54 AM > To: Burton M. Strauss III > Cc: [EMAIL PROTECTED] > Subject: RE: [Ntop-dev] Spreading ntop's RRD dumps to spread system load > > > Hi Burton, > > This patch makes the RRD thread die when doing the RRD updates: > > Jun 12 16:04:41 ntop ntop[20333]: [MSGID0067366] Starting 'rrdPlugin' > Jun 12 16:04:41 ntop ntop[20333]: [MSGID0529826] RRD: Welcome to > the RRD plugin > Jun 12 16:04:41 ntop ntop[20333]: [MSGID0974000] RRD: Mask for > new directories is 0700 > Jun 12 16:04:41 ntop ntop[20333]: [MSGID9274544] RRD: Mask for > new files is 0066 > Jun 12 16:04:41 ntop ntop[20333]: [MSGID0704862] RRD: Started > thread (-1140851792) for data collection. > > (...) > > Jun 12 16:04:55 ntop ntop[20375]: [MSGID9089762] RRD: FORK starting child > Jun 12 16:04:55 ntop ntop[20333]: [MSGID0940042] RRD: FORK ending parent > Jun 12 16:04:55 ntop ntop[20333]: [MSGID0554110] **WARNING** > THREADMGMT: rrd thread (-1140851792) terminated > Jun 12 16:04:55 ntop ntop[20375]: [MSGID0889950] RRD: FORK > dumpMatrix test > Jun 12 16:04:55 ntop ntop[20375]: [MSGID0346494] RRD: FORK > ending child, 318 RRDs updated > > Any other suggestions? ;) > > Regards, > Robbert > > > -----Oorspronkelijk bericht----- > > Van: Burton M. Strauss III [mailto:[EMAIL PROTECTED] > > Verzonden: donderdag 10 juni 2004 17:26 > > Aan: [EMAIL PROTECTED] > > CC: Kouprie, Robbert > > Onderwerp: RE: [Ntop-dev] Spreading ntop's RRD dumps to spread system > > load > > > > > > Interesting... > > > > That's actually easy to do in SOME situations, namely those that do > > copy-on-write on a fork() call. The fork()ed child gets a > > copy of memory as > > of the fork() call and can happily do what it wants with it - > > subsequent > > updates won't impact it. > > > > I haven't done a lot of testing, but give the enclosed patch > > (vs. 3.0) a > > try. > > > > Unfortunately that won't run in all OSes. > > > > For the others, I guess the question is, can you live with > > the RRDs being > > out of time-sync? > > > > -----Burton > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > > Behalf Of Kouprie, Robbert > > > Sent: Thursday, June 10, 2004 7:50 AM > > > To: [EMAIL PROTECTED] > > > Cc: [EMAIL PROTECTED] > > > Subject: [Ntop-dev] Spreading ntop's RRD dumps to spread system load > > > > > > > > > Hi Luca, ntop-dev, > > > > > > (Luca, we talked a little bit about this already - so this just > > > serves as a reminder and to inform ntop-dev). > > > > > > Just an idea for something I stumbled upon with the RRD dump > > > option in ntop. When RRDdumping to a large number of different > > > RRDs the system load gets a big spike. For example, when enabling > > > host RRD dumps in our setup (on a /16 net with about 25k active > > > hosts) it has to update *a lot* of rrds. Although I use a RAID10 > > > setup on SCSI disks, still the system gets a high load spike when > > > it's dumping time. > > > > > > Maybe it is an idea to spead the total disk I/O (i.e. the RRD > > > dumps) within the interval that is set to do the dumps. (So very > > > simply put: why do 25000 RRD updates once in 5 minutes, instead > > > of 5000 each minute in this 5 minute interval?). > > > > > > Regards, > > > Robbert > > > > > > _______________________________________________ > Ntop-dev mailing list > [EMAIL PROTECTED] > http://listgateway.unipi.it/mailman/listinfo/ntop-dev _______________________________________________ Ntop-dev mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
