Hi! I am in the process of evaluating the possibility to "correct" the current behaviour WRT manipulating socket buffer sizes...
So far I could understand from reading tons of docs found all over the internet, the socket buffer sizes are crucial for optimizing the network peformance related to fast, high-latency links. We have customers that would benefit from this so I need to find the way to make this happen in the Naviserver. I did find out that different OS'es handle such cases differently. Most of them require admins to tune either system or per-app buffer sizes to achieve good BDP (Bandwidh-Delay Product). Some (newer Linux'es) do this automatically. Currently we do already manipulate the socket buffer sizes in the main driver code (only). Unfortunately this manipulation happens (at least for the read-buffer-size) too late! As I understand, the socket buffers for reading must be setup BEFORE listen() call. Whereas we manipulate the sizes AFTER the connection is established. Furthermore, the Tcl API commands related to sockets (like ns_socklisten et.al.) also need to be expanded to allow for explicit buffer size manipulation. This all would definitely require some internal changes perhaps even adding new Ns API calls. I wonder if anybody already thought about this topic and what was the outcome? Cheers Zoran ------------------------------------------------------------------------------ _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
