On Mon, May 10, 2010 at 10:39 AM, Vasiljevic Zoran <z...@archiware.com> wrote:
> 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.
We talked about this in summer 2008, I think. It will be in your mail
or mailing list archives somewhere...
> 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.
Newer is relative. I think by now this means any linux, bsd, solaris
less than a decade old...
> 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.
Which code are you looking at? IIRC, you removed this code years ago:
http://bitbucket.org/naviserver/naviserver/changeset/a6e8a6348da0
------------------------------------------------------------------------------
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
