ntop's ability to handle traffic is going to depend on the network it's monitoring.
I'm trying to solicit measurement information to quantify what it can handle (CPU and memory) However, we do know that the # of active hosts and # of active sessions are the biggest influence on memory usage. The number of packets/second is the piece that I expect will be CPU sensitive. That said, a big enough box should be able to handle 3x100 Mbps, but be aware that with three SATURATED links you're getting close to the memory bandwidth of many Intel Pentium III computers. (But my memory is fuzzy about the details here). -----Burton -----Original Message----- From: Christian Hammers [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 11, 2002 8:59 AM To: Burton M. Strauss III Cc: [EMAIL PROTECTED] Subject: Re: [Ntop-dev] still have missing data in netflow export On Thu, Apr 11, 2002 at 08:55:46AM -0500, Burton M. Strauss III wrote: > It's not a time-based send, it's based on filling flow packets. Look at > netflow.c, specifically static void sendNetFlow(int sendPartialPak) {} > netflow.c's exclusion (look in void sendUDPflow()) is for the very specific > case of our flows. thanks > You haven't given much information about the network - is it possible that > ntop is simply not able to keep up and losing traffic? It's only about 300 to 400kbit/s. It should handle three 100MBit/s NICs. Err... ntop is capable of doing this, isn't it?!?! bye, -christian- -- Christian Hammers WESTEND GmbH - Aachen und Dueren Tel 0241/701333-0 [EMAIL PROTECTED] Internet & Security for Professionals Fax 0241/911879 WESTEND ist CISCO Systems Partner - Authorized Reseller _______________________________________________ Ntop-dev mailing list [EMAIL PROTECTED] http://listmanager.unipi.it/mailman/listinfo/ntop-dev
