Hello, I've read the previous threads concerning memory eating and hash sizes, and the information regarding a solution/fix to the supersizing of NTOP is pretty scarce.
I run 2.1.55 (sourceforge), using a Pentium MMX 166, 84 megs of RAM. I run it with the following command line: ntop -c -u ntop -m xxx.xxx.xxx.xxx/24, 192.168.0.0/24 -w 8080 -i eth0,eth1 I use the sticky hosts option since the hosts in my network generally connect for short periods of time and then dissapear, so dynamically purging the hash doesn't work for me. After about 5 minutes, NTOP drives the server load to about 2.8, and if left unattended it can reach 25. I would think this is a lack of hardware power issue, but I've managed various times to get ntop to use a very small memory footprint (12M) with this same command line during a high day traffic and keep that footprint for over 48 hours. I haven't found the right formula so far to be able to repeat this behaviour constantly. I tried using a SQL server to store host data, but it still drives memory usage thru the roof. What do you recommend to do in my case? Juan Puchalski _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop
