Re: Wicket scalability
On Thu, Oct 28, 2010 at 3:54 PM, Jan Luehr wrote: > Hello, > > I'm still trying to get into wicket - this time, I stumbled up on: > http://javathoughts.capesugarbird.com/2008/01/year-of-wicket.html > > It says: > "The application was a management console for an enterprise application. It > did not require high user traffic, so were weren't concerned about what > people talk about as the biggest issue with Wicket, namely scalability. We > certainly have had no performance problems ourselves." > > Although this article was written some months ago, I didn't notice any > concerns refering to scalability. > Do you know, what the author is referring to? > That should be worded "as expected, we did not encounter what people often cite as a common misconception about Wicket, namely, that it does not scale well". People commonly spread FUD about whatever framework doesn't seem to fit their needs. The common thing to say about Wicket is that it doesn't scale well. They say that holding state in the session kills scalability. However, to clarify the simplest: that's wrong, and has been disproven by numerous examples and benchmarks. Can you write a Wicket application that won't scale? Certainly! But give me any framework and I'll write you an application that will crash. The real question is: can you write a Wicket application that scales well? The answer is: ABSOLUTELY! Here are some really great benchmarks that you may find useful: http://ptrthomas.wordpress.com/2009/01/14/seam-jsf-vs-wicket-performance-comparison/ http://ptrthomas.wordpress.com/2009/09/14/perfbench-update-tapestry-5-and-grails/ -- Jeremy Thomerson http://wickettraining.com *Need a CMS for Wicket? Use Brix! http://brixcms.org*
Wicket scalability
Hello, I'm still trying to get into wicket - this time, I stumbled up on: http://javathoughts.capesugarbird.com/2008/01/year-of-wicket.html It says: "The application was a management console for an enterprise application. It did not require high user traffic, so were weren't concerned about what people talk about as the biggest issue with Wicket, namely scalability. We certainly have had no performance problems ourselves." Although this article was written some months ago, I didn't notice any concerns refering to scalability. Do you know, what the author is referring to? Thanks, Keep smiling yanosz - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket scalability
this has been my experience. anecdotal evidence and experience tells me that wicket itself is exceptionally fast. fast enough that your DB will definitely be the bottleneck and not by a bit, but by an order of magnitude. 1000/rps vs. 100rps kind of thing. Johan Compagner wrote: > > What do you mean with Scaling? > Wicket scales pretty well. because we fully support clustering out of the > box. > So you can add just add new servers. > > Wicket it self is fast, the database would be much more of a bottleneck. > > johan > > > On 9/19/07, Lowell Kirsh <[EMAIL PROTECTED]> wrote: >> >> For work I'm trying to use wicket, but my boss wants to be reassured >> that it will scale well. Can anyone point me to any sources (not >> anecdotes) about how well wicket scales? And yes, I know my question >> is vague, but right now, so are our requirements. >> >> Thanks, >> Lowell >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > -- View this message in context: http://www.nabble.com/wicket-scalability-tf4479322.html#a12791020 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wicket scalability
On 9/19/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > On 9/19/07, Lowell Kirsh <[EMAIL PROTECTED]> wrote: > > For work I'm trying to use wicket, but my boss wants to be reassured > > that it will scale well. Can anyone point me to any sources (not > > anecdotes) about how well wicket scales? And yes, I know my question > > is vague, but right now, so are our requirements. > > The best way to go is to not take our word for it, but test for > yourself. Take wicket-examples, create a test project at it (e.g. > using JMeter) and see what you got. Please feel free to post your > results. > > Matej, if you still have some of those JMeter results lying around, > maybe that would be interesting. Some results of testing for memory consumption I just ran on the app I'm working on (Wicket 1.3): Run 1: 3,000 sessions -> ~ 200 MB Run 2: 10,000 sessions -> ~ 950 MB Run 3: 10,000 sessions -> ~ 110 MB (very light page) Run 4: 10,000 sessions -> ~ 650 MB It depends on what your current page is (when you use the SecondLevelCacheSessionStore which is Wicket 1.3's default) and of course what is in your session object. Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wicket scalability
What do you mean with Scaling? Wicket scales pretty well. because we fully support clustering out of the box. So you can add just add new servers. Wicket it self is fast, the database would be much more of a bottleneck. johan On 9/19/07, Lowell Kirsh <[EMAIL PROTECTED]> wrote: > > For work I'm trying to use wicket, but my boss wants to be reassured > that it will scale well. Can anyone point me to any sources (not > anecdotes) about how well wicket scales? And yes, I know my question > is vague, but right now, so are our requirements. > > Thanks, > Lowell > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: wicket scalability
On 9/19/07, Lowell Kirsh <[EMAIL PROTECTED]> wrote: > For work I'm trying to use wicket, but my boss wants to be reassured > that it will scale well. Can anyone point me to any sources (not > anecdotes) about how well wicket scales? And yes, I know my question > is vague, but right now, so are our requirements. The best way to go is to not take our word for it, but test for yourself. Take wicket-examples, create a test project at it (e.g. using JMeter) and see what you got. Please feel free to post your results. Matej, if you still have some of those JMeter results lying around, maybe that would be interesting. Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
wicket scalability
For work I'm trying to use wicket, but my boss wants to be reassured that it will scale well. Can anyone point me to any sources (not anecdotes) about how well wicket scales? And yes, I know my question is vague, but right now, so are our requirements. Thanks, Lowell - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
