On Mon, May 11, 2009 at 12:10 PM, Thiago H. de Paula Figueiredo <thiag...@gmail.com> wrote: > Em Mon, 11 May 2009 14:26:16 -0300, Neil Curzon <neil.cur...@gmail.com> > escreveu: > >> Tapestry 5.0.18:
I missed this earlier; yes, 5.0.18 had not yet been optimized for memory or speed. Anything in the 5.1, preferable 5.1.0.5 the stable release, would perform better. >> Requests per second: 776 >> Average resp time (ms): 25.41075 > > Have you tried Tapestry 5.1.0.5? There were some improvements in the > rendering process starting at 5.1.0.1. > > Another issue is to have the same machine being the client and the server > and the number of concurrent threads. The best scenario is having one > machine as the server and N others as the clients, because you don't have > threads in the same machine trying to use the same shared resource (the > network stack and adapter). > > By the way, I have a little of benchmarking experience and all the hints > given by Christian are absolutely correct. > > -- > Thiago H. de Paula Figueiredo > Consultor, desenvolvedor e instrutor em Java > http://www.arsmachina.com.br/thiago > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry Director of Open Source Technology at Formos --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
