we did stress testing of a pretty complex ui at thoof and found we could handle something like 20,000 sessions under simulation on a webnode pair with full failover.
i am aware of sites (who will remain nameless for a while, unfortunately) with millions of users who are switching to wicket. i was not 100% sold on wicket's broad applicability in the first year or two, but now that i have experience with it (and the team has broadened and deepened it) i would not use another web technology for any /server-side/ html-over-http web project whatsoever (i think GWT and other similar client-side technologies are complementary to wicket). i think even high-volume, truly stateless applications could benefit from wicket's component model and markup handling. of course, i might be biased. ;-) Vitaly Tsaplin wrote: > > No, I am not advocating JSF at all :) I agree with all you gays. > Wicket is just like a fresh air in a web development. I am just trying > to realize what is the price to pay for such a pleasure :) > > On Mon, Mar 17, 2008 at 1:01 PM, Martin Makundi > <[EMAIL PROTECTED]> wrote: >> Wicket is just so much more efficient to code you do not need so many >> developers... >> >> 2008/3/17, Vitaly Tsaplin <[EMAIL PROTECTED]>: >> >> >> > I am just looking at the number of job offers for JSF :) It's a >> > lot! That demand means that there are a lot of development in JSF. >> > >> > On Mon, Mar 17, 2008 at 11:38 AM, Johan Compagner >> <[EMAIL PROTECTED]> wrote: >> > > where is the complex JSF app that has many many concurrent users? >> > > Most of the time the more complex the app gets the less concurrent >> users it >> > > will have. >> > > Because those kind of complex apps are mostly targetted at a >> specific group >> > > of people. >> > > >> > > Where are for example Enterprise level apps just open on the >> internet? >> > > >> > > On Mon, Mar 17, 2008 at 11:20 AM, Vitaly Tsaplin >> <[EMAIL PROTECTED]> >> > > >> > > >> > > wrote: >> > > >> > > > Hi Johan, >> > > > >> > > > Many thanks for your answer. >> > > > >> > > > A real world enterprise level app is usually about complex >> user >> > > > interface and many many concurrent users at one time. >> > > > >> > > > When I told about real world applications I meant mostly a >> > > > comparison with some other popular frameworks like JSF. It >> wasn't >> > > > obvious, sorry :) I mean having a framework which is at least >> not less >> > > > efficient then JSF automatically implies that we can do all that >> stuff >> > > > which is done with JSF. So in its turn it means that wicket is >> > > > perfectly suitable for enterprise level apps as well as JSF. I >> do not >> > > > mean that JSF is a good choice but it's proven in practice. >> > > > >> > > > Vitaly >> > > > >> > > > On Mon, Mar 17, 2008 at 10:33 AM, Johan Compagner >> <[EMAIL PROTECTED]> >> > > > wrote: >> > > > > we have our own threadtest (see svn) to test scaling >> > > > > >> > > > > What is a real world enterprise level app? >> > > > > >> > > > > Is that about the complexitiy of the user inteface and the >> application >> > > > > itself? >> > > > > or is it that it is used by many many concurrent users at one >> time but >> > > > the >> > > > > app is pretty simple? >> > > > > >> > > > > About design principals, use detachable models everwhere to >> keep the >> > > > state >> > > > > als low as possible, >> > > > > To be Highly responsive doesn't mean that you have to have a >> memory >> > > > > inexpensive app. >> > > > > >> > > > > Wicket apps do use session memory for pages, For 1.3 only 1 >> page per >> > > > > pagemap, so most of the time 1 page per session/user >> > > > > And what a page cost in mem is very dependend on the >> complexity. >> > > > > >> > > > > johan >> > > > > >> > > > > >> > > > > On Mon, Mar 17, 2008 at 10:01 AM, Vitaly Tsaplin < >> > > > [EMAIL PROTECTED]> >> > > > > wrote: >> > > > > >> > > > > >> > > > > >> > > > > > Hi everyone, >> > > > > > >> > > > > > Does anyone try to do any scalability tests with wicket? >> How is it >> > > > > > suitable for real world enterprise level applications? And >> the most >> > > > > > important question: What are the design principals I should >> follow in >> > > > > > order to turn my homemade application into a real, highly >> responsive >> > > > > > and memory inexpensive app? Where can I read about it? >> > > > > > >> > > > > > Vitaly >> > > > > > >> > > > > > >> --------------------------------------------------------------------- >> > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > > > > > For additional commands, e-mail: >> [EMAIL PROTECTED] >> > > > > > >> > > > > > >> > > > > >> > > > >> > > > >> --------------------------------------------------------------------- >> > > > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > > > For additional commands, e-mail: [EMAIL PROTECTED] >> > > > >> > > > >> > > >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Is-wicket-an-efficient%2C-enterprise-level-web-framework--tp16090688p16114253.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
