First of all let me state that this is not really a tapestry question but more of a general J2EE app server thing.
Anyway, it is not really possible to give some real numbers because the whole performance and scalability behaviour is very strongly related to the things that your code does and the way you programmed it, not to mention the way the user walks through your site. I would strongly suggest that you test your application and monitor how much ram it needs and how performance numbers (render time being one parameter) changes with more users. There are a number of tools for doing this freely available. One that I find quite usable and easy to use is the "Web Application Stress test tool" that is available for free from Microsoft (http://www.microsoft.com/technet/archive/itsolutions/intranet/downloads /webstres.mspx?mfr=true). Basically it works a proxy for your browser and measures all page generation times etc. from recorded scripts. Try that with different numbers of threads (simulated users) and you get some numbers to start from. As long as it is not required by some specs or management decisions I would keep the whole scenario as simple as possible and only tune what needs to be tuned. Like always: the more cpus, the better; the more ram, the better. Unless you do not have performance numbers it does not make any sense to give recommendations what hardware you need. I have been involved in projects where just the app server had 8 processors and 8 gb of ram and wasn't possible to accept more than 100 users simultaneously because of extremely complicated business rules and extreme amounts of data (that was no shop, of course). On the other hand I have two shops on one machine that can (according to my tests) easily handle up to 500 users with a single cpu and 1 gb of ram. Often it is the architecture of the app, not the hardware you use that decides how far your application scales. Check if you can cache anything, that could save you the money for another cpu. Cheers, Detlef -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 23 March 2006 12:50 To: Tapestry Subject: Tapestry hardware recommendations I'm planning on going production in 2-3 months and I'm wondering what kind of hardware and configurations you guys recommend for live tapestry applications. I would appreciate any recommendations, options and ( of course ! ) war stories. I hope that the upcoming weekend would allow for extended replies. Environment : windows server jdk 1.5 tomcat 5.5 tapestry 4.0 oracle 10g as database ( on a separate machine ) dbcp Application : kind of a generic e-shop application ( with its own quirks , of course ) connection through http ( no https ) about 15 pages guaranteed no less than 200 and no more than 250 users at any moment at any given moment 80% of the users will be viewing one particular page ( list of goods ), which does some db lifting and takes ~2 seconds to render I would expect that each user will send one request per minute Questions : 1. what amount of RAM should app server have ? 2. what part of RAM should be dedicated to java ( i.e. -Xmx512m -XX:MaxPermSize=512m ) ? 3. what kind of cpus ( GHz ) 4. # of cpu per server 5. does java scale well between the processors or should I run several instances of tomcat ? 6. what is your recommended number of threads ( in tomcat config file ) 7. are there any other config options I should pay attention to ? Thank you. --------------------------------------------------------------------- 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]
