On Wed, 23 Jun 2010 16:26:44 +0200, Emmanuel Lecharny <[email protected]> wrote: > FYI, I committed some modification to get rid of the default sizes. It > should now default to the OS default value.
I had a look on it. Now the line in NioSocketAcceptor is gone. So by default, there is no socketconfig like socket read buffer size overwritten by mina. It now uses the system default. Fine. But this fix isn't complete, or? If I now set the read buffer size with the session config object, it's simply stored in the member variable, but not passed to the socket. And same with getting the read buffer size. The session config simply return the member variable, without gathering anything from socket. > > more inline... > > On Wed, Jun 23, 2010 at 4:16 PM, Alexander Christian <[email protected]> wrote: > >> >> Yes, I found the same while searching for the "ideal buffer size". I also >> thought about setting/resetting the buffer size during connection. > > > You can't change it once the session is established, at least, on the > server side. Hmm, I was not sure if it's possible or not. To be honest, I also did not try it out ;-) > > >> But for >> this I need the current bandwidth, which is, if it's not a connection >> between two dedicated servers, but rather one dedicated server and a >> ADSL, >> very complex I think. Other applications running on the same client can >> have an impact ion the overall performance :-( >> > > At this point, it's really about tuning. The default OS value should be > fine > 80% of the time, and if you know more about the real usage, then you can > tune a bit more. Yes, I can agree with this. br, Alex
