On Thu, Sep 22, 2011 at 8:16 PM, Edouard De Oliveira <[email protected]> wrote: > @ashish he already did like said in a previous mail but it didn't change much > as well
oops i missed that... i tried adding Executor filter as well, but it made my results worse :( > > @bluedavy i'd like to know what are exactly the parameters used to start the > client and the server ? (timeout , concurrents, byte size etc ...) > also plz note that this link is broken > : http://bluedavy.com/projects/nfs-rpc/benchmark-1.xslx > > Cordialement, Regards, > -Edouard De Oliveira- > > > ----- Mail original ----- > De : Ashish <[email protected]> > À : [email protected]; Edouard De Oliveira <[email protected]> > Cc : > Envoyé le : Jeudi 22 Septembre 2011 15h24 > Objet : Re: Re : new benchmark results for mina1/mina2/grizzly/netty > > On Tue, Sep 20, 2011 at 7:33 PM, Edouard De Oliveira > <[email protected]> wrote: >> First you could try enabling some socket options (like on the others >> frameworks) to the mina2 test : >> >> server side add these before bind : >> >> ((NioSocketAcceptor) acceptor).setReuseAddress(true); >> ((NioSocketAcceptor) acceptor).getSessionConfig().setTcpNoDelay(true); >> >> client side add after the setTcpnodelay line : >> ioConnector.getSessionConfig().setReuseAddress(true); >> >> >> what are the new figures with these settings ? >> >> Cordialement, Regards, >> -Edouard De Oliveira- > > @Edouard - updated the benchmark code with your suggestions. Did > marginally increased TPS on my laptop :( > > @bluedavy - can you rerun the test again. > > thanks > ashish > > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
