Hi David, Bummer.
If you run top, what % of CPU usage is System? On our box I noticed that System would often be as high as 98% and the userland processes would still be very low. To me this indicated that either the kernel or NIC drivers, were the bottleneck. Again, in our case it was high volumes of small packets (our DNS had gone nutz and was spewing out a huge number of UDP DNS packets). A faster CPU probably would help here, though the NIC and it's drivers are probably just as important. Not sure about ntop and SMP, though since it's multithreaded, it probably does see some benefits. Good luck with the fxps. We're dual Intel Gigabit Quad cards here... over kill on bandwidth, but we need the number of interfaces. > tcpdump with DNS resolution to file is OK : > probe# tcpdump -i fxp1 -w tcp.dump > tcpdump: WARNING: fxp1: no IPv4 address assigned > tcpdump: listening on fxp1 > ^C > 192737 packets received by filter > 0 packets dropped by kernel > ntop uses "only" 25 to 30% of CPU. > interrupts is less than 5% > > I guess faster CPU is still the answer ? > At least, kernel/NIC is not the problem. > > Is ntop able to run with several threads on a SMP system ? > > > I know I'm having a lot of small udp packets (due to game > servers hosting). > > I'll make a try tomorrow with another fxp card chipset release. _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop
