All:
I've been running ntop for about 3 weeks. I'm running on a Dell 1750
with a pair of 3.2 Ghz processors. I'm running ntop 3.3.6 sourced from
the RedHat EPEL yum repository. After figuring out and installing all
the requirements my Local Network Map works fine as long as there are <
500 hosts. After that it becomes hit or miss. At > 800 hosts all I get
in the browser is a broken image file. With large numbers of hosts (>
800) dot runs at 100% of cpu for 2-3 minutes. When it ends all I get in
the browser is a broken link. I'm not getting any errors in my logs.
I have a suggestion about the Local Network Map:
This feels like a timeout of one sort or another. It seems to me
that instead of regenerating the image map every time the
networkMap.html URL is hit, a better approach would be to run these
updates in the background, generate static objects then pass these to
the browser. That way the browser/server are not subject to timeouts or
volume related issues and the user gets reasonably current data. The
thread/process could even be "niced" down so as to not effect other
workloads. Perhaps the frequency of update could be configurable, with
a reasonable default like 300 seconds.
If there is a workaround for this apparent capacity problem please let
me know. Other then that TIFWIW. This is not a critical feature (to me)
just a "Nice to have", though it would be "Nicer to have" during my peak
periods. :)
Best Regards,
Jim
_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop
