I'm working on a server that needs to send rather small packets and about 15 of them every second i've just been going over the usage and it seems i need around 40 bytes per packet (20 ip + 20 tcp) just for the header
so 1200 bytes on the header and 165 bytes of data per second
not sure if i've worked that out right but if its true then thats a lot of overhead for such a small amount of data
i was considering using udp which would reduce that to 720 bytes however i was hoping if i could go any further
would raw sockets allow me to save even more? and even with the restrictions imposed by microsoft since xp sp2 is it still possible to make any real use of raw sockets or it simply not worth the effort?
i'm planning to receive 15 packets from approximately 40 connections so with tcp thats around 200MB an hour just to deliver 24MB worth of content (combining the packets together is not an option)
Question
DDStriker
I'm working on a server that needs to send rather small packets and about 15 of them every second i've just been going over the usage and it seems i need around 40 bytes per packet (20 ip + 20 tcp) just for the header
so 1200 bytes on the header and 165 bytes of data per second
not sure if i've worked that out right but if its true then thats a lot of overhead for such a small amount of data
i was considering using udp which would reduce that to 720 bytes however i was hoping if i could go any further
would raw sockets allow me to save even more? and even with the restrictions imposed by microsoft since xp sp2 is it still possible to make any real use of raw sockets or it simply not worth the effort?
i'm planning to receive 15 packets from approximately 40 connections so with tcp thats around 200MB an hour just to deliver 24MB worth of content (combining the packets together is not an option)
thank you in advanced :)
Link to comment
Share on other sites
5 answers to this question
Recommended Posts