Why is tracking so memory hungry
Wed, 27 Feb 2002 13:00:10 +0100 (CET)
On Wed, 27 Feb 2002, Schramp, R. wrote:
> Hello All,
> First, thanks for the fast response, I am still a bit puzzled though.
> > > I understand from this statement that the amount of data
> > needed is about
> > > 16Kbyte per connection, of which 350 bytes is non
> > swappeble. This seems like
> > > an awfull lot of data for one TCP session.
> > where do you get the 16k from? it's 350 bytes.
> Well 16Kb is the number I get when I device 64Mb by 4096.......
> Am I correct when I conclude that the FAQ is incorrect???? (My puzzlement
> starts here, no flame intended...)
it's 350 bytes per connection, but the default number of connections
is calculated with memorysize/16384 , you don't want to lock
upp all of your memory in the machine if you are victim of an DoS attack
or something similar
64*1024*1024/16384 = 4096 connections as default on a machine with 64MB ram
and each of those connections use 350byte of memory so
4096*350 = 1433600 bytes (1.4MB) for those 4096 connections.
Never argue with an idiot. They drag you down to their level, then beat you with experience.