I found that on a quad core I would have graphing issues when I had about 1000 data sources but I also have ciscoworks on the same box with 2k3 sp2.
I also found that graphing is much more accurate when you set the priority of the dude to high or real time with sysinternals process explorer. I also reduced my data sources to about 400. I was pinging every computer on the network as a test to see how many got shut off over night.
ok Im running the dude on a box and the client from my laptop…But I still have data sources that do not graph…!!AS#@!A!
Sometimes I change the interval from 30 seconds to 20 seconds and that seems to jumo start it…But doing that every few days for 50 data sources is a nightmare…
Have a look at my attachments…The probe-function.jpg shows my configurations to pull the stats from the Mikrotik…and the service graphs shows that the dude gets the values from the mikrotik when I add the custom probe to the device, but for some reason the graphs do not show…