IraqiGeek wrote:> On Sunday, January 08, 2006 1:38 AM GMT, Simon <@Simon3> wrote:
Can you tell me how you can handle more than 2000 connections to you
server, without the need for maxing out the amount of RAM in the PC?
forget about maxing memory, how the heck is he able to handle up to 4GB
body the MTU is 1500 bytes on LAN (8KB if you use jumbo frames on GbE),
not to count all the TCP overhead, and still maintain “minimum latency”
I agree, this large buffer can never work on a high end server.
I’ve checked a couple of protocols and the best way I found to do my
project, is to use a combination of ICMP, TCP and UDP. All of them will
have small buffers since I prefer to drop information rather than being
DoS or maybe have to ignore more connections.
forget about maxing memory, how the heck is he able to handle up to
4GB body the MTU is 1500 bytes on LAN (8KB if you use jumbo frames
on GbE), not to count all the TCP overhead, and still maintain
"minimum latency"
I agree, this large buffer can never work on a high end server.
without wanting to sound rude, i don’t think you have understod, how
this works.
initial buffer size is 4kb. if you do not send larger packets than 4kb,
the buffer size will never increase to more. even if somebody sends a
broken header, there is no problem yet, because mallocing a large
buffer without using it, will not claim more memory.
putting an upper limit of buffer size, depending on your high level
protocol is trivial.
I’ve checked a couple of protocols and the best way I found to do my
project, is to use a combination of ICMP, TCP and UDP. All of them
will have small buffers since I prefer to drop information rather
than being DoS or maybe have to ignore more connections.
sounds really complicated and i can not imaging how ICMP could be
useful here, but who knows.