Mark pretty much beat me to the punch but... What is the size of the database? How intense are the hits to the database? Fault Tolerance is an important question. If everything is small enough it could all be on one server and still easily support 40 sessions. But like Mark said, are you absolutely sure it will never be more? Giving specs without having more details is very difficult. How you implement will greatly affect the specs of the hardware. Virtual Servers? All on separate physical machines? Michael Ward Redhat Linux Administrator Metro State College of Denver 303-352-4225 -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of m.roth@xxxxxxxxx Sent: Tuesday, September 15, 2009 8:00 AM To: General Red Hat Linux discussion list Subject: Re: Please suggest server configuration > Hello Everyone, > > i know this is not the right place to post this query, however i want to > seek opinion of all the smart sys admins here. > > ****************************************** > > I am expected to recommend a hardware configuration for an application > that my company has developed. The application setup includes : > > 1. tomcat server ( the front end that would run the webpages) > 2. Jboss server (application server, that would do the heavy computing and > READ-WRITE to the database) > 3. Mysql server. > > We want the server configuration to support 40 simultaneous user sessions. <snip> I actually asked something similar months ago. A couple of things come to mind, though: 1) is this some kind of internal website - only 40 user sessions? If so, the basic configurations will handle way more than that. 2) are you 150% positive it will only ever need to support 40 user sessions, and that a year from now, they won't want to let 400 or 4000 users on? 3) Is there budget for more than one physical server? For my points 1 & 2, you should *always* plan for max usage, not median, so overspec. For my point 3, for a real production system, I'd have the web server on one box, and the d/b on another. And a third, running both, for development and q/a. The latter doesn't need to be as heavy as the production boxes, though. *Maybe*, for such a small operation, you might be able to get away with one production box for all. Oh, and think about what happens if you loose something - what's the impact of downtime if a drive goes out, or a NIC? mark -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
