http://httpd.apache.org/docs/2.2/programs/ab.html
I think you're correct with the params, but I've no idea about the cookies. I think that basic lesson is that the benchmark that was done is only of use if the OP intended to be serving the Wicket-Examples app out at that rate - otherwise a more representative web-app would be much better! /Gwyn On 09/08/06, Johan Compagner <[EMAIL PROTECTED]> wrote: > What is ab2 for a thing? > It looks like you are 1000 times getting that same bookmarkable page for 100 > threads? > That page is because of the source code viewer link not stateless so you a > creating pages that will go into the sessions. > Now is the question does ab2 work with cookies or not? If not then it does > create 100 * 1000 sessions and for all those it creates 1 page... > > > johan > > > On 8/9/06, Sebastjan Trepca <[EMAIL PROTECTED]> wrote: > > > > I used the default resin3pro configuration. I tested it like this: > > ab2 -n 1000 -c 100 > http://localhost:8080/wicket-examples-1.2/repeater?wicket:bookmarkablePage=:wicket.examples.repeater.DataGridPage > > > > It died after eating 100MB of memory and serving 600-800 requests*100 > threads. The problem is also that the CPU was on 100%. > > > > This version 2.0 sounds very nice, is it usable yet? > > > > How can I set a page to be stateless in 1.2.1 ? Is there some attribute to > do this or does it just mean that you use detachable models? > > > > I would definetly like to handle sessions separately and have all my pages > stateless. So forms are saved into sessions or what is the problem with > them? They seem very nice though. > > > > Thanks for help. > > > > > > Sebastjan > > > > > > > > On 8/9/06, Johan Compagner <[EMAIL PROTECTED]> wrote: > > > > > > I also stress tested the examples quite a lot. > > > > > > Which part did you test that you get an out of memory? And how much > memory did you give your server? > > > > > > Memory usage can be cut down in several ways: > > > > > > 1> use for heavy hit pages stateless pages (in 1.2 just use bookmarkable > links and no forms on it), in 2.0 you have much more choices for working > stateless. > > > 2> For none stateless pages, do use detachable models. Make sure that > you don't hold large (db) objects in your pages when they are serialized to > the http session. > > > 3> Tweak how many of those pages should be in memory. (this depends on > how far you want to go with the back button support) > > > in 2.0 we have a different session store that only keeps 1 page > in mem. And the rest is cached and stored to disk. > > > > > > > > > johan > > > > > > > > > > > > > > > > > > On 8/9/06, Sebastjan Trepca < [EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > > Hi all! > > > > > > We're starting a new project that will be quite big (1-2 million users) > so now I'm choosing a web framework to use. > > > It seems that Wicket is a very good framework but what worries me is the > performance and scalability. I installed wicket-examples on my machine and > stress-tested them a bit, just for curiosity, and always got OutOfMemory > error which didn't look very promising. Then I read about detached models > and created a project using them and it didn't crash anymore, but still, > memory was quite high. > > > Now I searched thru wiki and didn't find any other tips about > performance etc. > > > > > > So, do you have any tips for me, on design level or maybe links to other > docs, whatever really :) > > > -- Download Wicket 1.2.1 now! - http://wicketframework.org ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
