Hello, as of my experience there are two performance areas: - page/page part rendering performance - garbage collection and custom algorithms. - page delivery performance - caching.
Regarding the former one: - custom algorithms: By these I mean all software pieces implemented on request of the customer (whether external or internal), this includes all the experience and knowledge of the engineers (quality, performance and development) - garbage collection: As Java has a dynamic memory management engine it is very important to minimize the uncertainty of the functionality of the engine by exactly specifying how it has to work. Regarding the latter one: - If a page/page part has already been rendered, then it only has to be delivered - this is the most important objective to set. Normally you use a reverse proxy to immediately reply to known requests with cached responses. Andras Nino.Martinez wrote: > > Hi Guys > > We are having the potential fun of running a site with around 1 million > users, and a lot more over time. What could be great optimizing points? > > We have looked at these things > > * Detachable models (not sure if it makes anything run faster, just > that it keeps the memory footprint down making more users possible > on each server) > * Web Cache(Oscache, Ehcache or Apache http) > * Internal cache(Eh distributed cache) > * Clustering(simple web server clustering with apache > http/loadbalancer/tomcat) > o Would Jetty be better? > > Are there something we have forgotten? Have other point to pick out? > Should we investigate terracotta also(seems they integration are working > now)? > > -- > -Wicket for love > > Nino Martinez Wael > Java Specialist @ Jayway DK > http://www.jayway.dk > +45 2936 7684 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Running-a-huge-wicket-site%281m-%2B-users%29-tp18465923p18559076.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]
