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...) > > <SNIPPED FROM FAQ> > > If you notice the following message in syslog, it looks > like the conntrack > > database doesn't have enough entries for your environment. > Connection > > tracking by default handles up to a certain number of simultaneous > > connections. This number is dependent on you system's > maximum memory size > > (at 64MB: 4096, 128MB: 8192, ...). > > You can easily increase the number of maximal tracked > connections, but be > > aware that each tracked connection eats about 350 bytes of > non-swappable > > kernel memory! > > <END OF SNIP> > > Because the FAQ clearly states that 64Mb memory corresponds to 4096 connections. Or is the important word in this scentence "SIMULTANEOUS" which is not directly related to the total number of connections (e.g. answer "c" of my example). > > Also the FAQ is not completely clear to me on the mentioned memory > > requirements, eg a system with 64Mb physical memory and > 10Gb swap is capable > > of: > > a) 4096 connections = 64Mb/16k > > b) 655360 connections = 10Gb/16k > > c) 191739 connections = 64Mb/350 Is my misunderstanding comming from user space requirements (swappable) that are 16Kb per connection? Best Regards, Ruud Schramp
