On 10.05.2010, at 21:13, Stephen Deasey wrote:
>
> Looks like it would be a mistake to use setsockopt() on Linux >=
I know that. Therefore I said that some OS'es do this automatically.
For good or for worse I will (re)add this knobs and leave defaults to
zero (== no changes) in both driver code
On Mon, May 10, 2010 at 7:22 PM, Andrew Piskorski wrote:
> On Mon, May 10, 2010 at 11:39:26AM +0200, Vasiljevic Zoran wrote:
>
>> 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
On Mon, May 10, 2010 at 11:39:26AM +0200, Vasiljevic Zoran wrote:
> 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.
Sounds like what the hpn-ssh pa
On 10.05.2010, at 14:38, Stephen Deasey wrote:
>
> Should there be some way to 'ignore' this if the OS can handle it
> automatically? Maybe you just pass [ns_config socket bufsize] to the
> option and if it's 0, ignore it...?
Sure. This is what I wanted to do. On zero, ignore (== don't set).
As
On Mon, May 10, 2010 at 12:39 PM, Vasiljevic Zoran wrote:
>
> What I have in mind is to:
>
> a. make necessary changes to the driver code so that socket options
> are set before we actually call listen().
>
> The a. is really the most work as it will require either chaning
> existing (sub-optimal)
On 10.05.2010, at 12:55, Stephen Deasey wrote:
>
> Which code are you looking at? IIRC, you removed this code years ago:
>
>http://bitbucket.org/naviserver/naviserver/changeset/a6e8a6348da0
>
We do still have people using old'er OS'es and by scrapping this out
they were forced to change buffe
On Mon, May 10, 2010 at 10:39 AM, Vasiljevic Zoran 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 buf
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
fa
