severity 288006 wishlist
tags 288006 + wontfix
thanks

On Mon, Apr 25, 2005 at 10:51:26AM +0200, Jerome Warnier wrote:
> Le samedi 23 avril 2005 à 22:28 +0200, Ola Lundqvist a écrit :
> > Hello
> > 
> > One thing I need to know with this is how much memory you see as huge
> > memory usage?
> Several hundreds megabytes RAM in less than one week (200-300MB). The
> more you let it run, the more it grows.

It sounds a bit high but I can not say that it is a bug.
The more hosts you will find the more memory ntop need. There are says
to limit the number of hosts (by forgetting old ones) on which you
can read in the documentation.

> > And how much is a lot of traffic?
> Several hundreds megabytes a week (let's say 600-700 MB).

I have checked with upstream and this is expected behaviour. Ntop will
use lot of memory because it store every host it has collected data
for. Each host take a number of KB (> 8KB each) of memory. On my simple home
network ntop take more than 32 MB and it has not monitored more than
say 30 hosts.

So if you have a high load then you need a lot of memory on that host.

As upstream told. If you have a portscan on your net /24 you will be
hitted with more than 16 MB in just that portscan.

This is how ntop works so I will not fix this bug, more than trying
to fix ntop 3.1. It has better memory handling (no resize of hashes)
but it will not fix your major problem.

Regards,

// Ola

> > Regards,
> > 
> > // Ola
> > 
> > On Fri, Dec 31, 2004 at 06:05:31PM +0100, Jerome Warnier wrote:
> > > Package: ntop
> > > Version: 2:3.0-3
> > > Severity: important
> > > 
> > > It seems it has been a long time since ntop leaks memory (at least when
> > > running as daemon). You could already notice it in Woody, and this is
> > > still a big problem in Sarge. I even suspect ntop to make one of my
> > > servers crash a few days ago, after running several days on a quite busy
> > > network. Very difficult to trace indeed, though seing its huge memory
> > > usage is very easy.
> > > 
> > > Maybe the next release (3.1, released on 21st of Decembre) fixes this?
> > > The announce says "smarter memory usage".
> > > 
> > > Thanks
> > > 
> > > -- System Information:
> > > Debian Release: 3.1
> > >   APT prefers testing
> > >   APT policy: (500, 'testing')
> > > Architecture: i386 (i686)
> > > Kernel: Linux 2.6.8-1-686-smp
> > > Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
> > > 
> > > Versions of packages ntop depends on:
> > > ii  debconf                     1.4.30.11    Debian configuration 
> > > management sy
> > > ii  libc6                       2.3.2.ds1-18 GNU C Library: Shared 
> > > libraries an
> > > ii  libfreetype6                2.1.7-2.3    FreeType 2 font engine, 
> > > shared lib
> > > ii  libgd2-xpm                  2.0.33-1.1   GD Graphics Library version 2
> > > ii  libgdbm3                    1.8.3-2      GNU dbm database routines 
> > > (runtime
> > > ii  libglib1.2                  1.2.10-9     The GLib library of C 
> > > routines
> > > ii  libjpeg62                   6b-9         The Independent JPEG Group's 
> > > JPEG 
> > > ii  libpcap0.7                  0.7.2-7      System interface for 
> > > user-level pa
> > > ii  libpng12-0                  1.2.8rel-1   PNG library - runtime
> > > ii  libssl0.9.7                 0.9.7e-2     SSL shared libraries
> > > ii  libxml2                     2.6.11-5     GNOME XML library
> > > ii  zlib1g                      1:1.2.2-3    compression library - runtime
> > > 
> > > -- debconf information:
> > > * ntop/user: ntop
> > > * ntop/interfaces: bond0
> > > 
> > > 
> > 
> -- 
> Jerome Warnier <[EMAIL PROTECTED]>
> BeezNest
> 
> 
> 

-- 
 --------------------- Ola Lundqvist ---------------------------
/  [EMAIL PROTECTED]                     Annebergsslingan 37      \
|  [EMAIL PROTECTED]                 654 65 KARLSTAD          |
|  +46 (0)54-10 14 30                  +46 (0)70-332 1551       |
|  http://www.opal.dhs.org             UIN/icq: 4912500         |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
 ---------------------------------------------------------------


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to