Hi Ville !
9902468 wrote: > > Science favors measurable differences - if you make arguments please back > those up with hard numbers. You are absolutely right about numbers. Should I apologize for Tapestry site that misled me a lot - I think I should not. After I received clarifications from Igor and others I immediately concluded that there is no much reasons for Tapestry to bee too slow. Nevertheless I did some measurements once I got some time. I have installed Tapestry, Jetty, OpenEJB and Jumpstart following the instructions. Then I have installed jmeter. I set it for 30 threads 100 seconds for a warm-up and 500 requests from each thread. The request did hit only the first page of Jumpstart - localhost:8080/jumpsatrt/ itself. The numbers are: average response time 130 milliseconds, throughoutput - 130/second. Not bad at all. I ran jetty from eclipse as described in the instruction. To test HybridJava I ported same page into HybridJAva format and generated war file which I installed under jetty and ran jetty from a command line. HybridJava is only about twice faster. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Re-HybridJava-vs-Tapestry-tp3555989p4287677.html Sent from the Tapestry - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
