Hardware guidelines for webservers
Reber, Simon
simon.reber at roche.com
Thu Apr 16 12:33:00 UTC 2009
Mark,
Well, I really have to tell you that I don't have any number available
for you :-(
But maybe somebody else or maybe friend Google ;-)
The only thing I can give you as hint is the fact I already mention in
my previous mail:
-> CPU power isn't that important (of course a runqueue full of
requests isn't nice but I've never seen something on a webserver before)
-> Network and Disk speed/handling are important for performance
of a webserver (and maybe memory)
I think your approach with two physical server and on top some VM's
(they can BTW easily extended when vertical scalability is an option) is
good enough for the beginning.
Since I don't want to favor any hardware vendors are I am not going to
tell you which vendor or product you should take.
But from my perspective should it be OK to take something cheap
with maybe 2 Dual Core CPU's, 4 GB memory and (if no SAN is present) an
internal
disk of about 500GB
Cheers,
Simon
>-----Original Message-----
>From: redhat-list-bounces at redhat.com
>[mailto:redhat-list-bounces at redhat.com] On Behalf Of mark
>Sent: Thursday, April 16, 2009 2:19 PM
>To: General Red Hat Linux discussion list
>Subject: Re: Hardware guidelines for webservers
>
>Simon,
>
>Reber, Simon wrote:
>>
>> I assume that the entire topic is about a webserver (according to the
>> subject it must be ;-)
>
>Yep. What looks to be a small contract to recommend and then
>install for me...
>and I've never done the first part before.
>>
>> Well for this kind of topic it's always difficult to give you a
>> satisfying answer since it depends on what kind of web
>application you
>> want to run.
>> From a money perspective is it also important how you want to
>> scale the web application (horizontal or vertical)
>>
>> But to the real facts.
>> My experience with this topic is more or less simple.
>> For a simple webserver, which is serving static pages, you don't
>> need much of CPU power (usually fast disk access is enough)
>> For a webserver with dynamic pages and maybe a small db it is
>
>Except I'm waiting now to find out what kind of hits to
>expect. This is not a
>personal site, but a business site, and they *could*,
>theoretically, get a good
>number of hits. That's why I need to have some kind of numeric
>guidelines. I'm
>figuring on virtualization, and at least two real servers for
>the web with two
>VM's on each, and another for the d/b; don't begin to know
>enough to know
>whether we'll need to mirror the d/b.
>
>> also sufficient to have a low cost hardware (expect if you
>need to be HA
>
>Um, low cost for rack mounts, that is.
>
>> ... But this
>> can also be done with load balancer, etc.)
>
>I know. Not sure whether they'll need, or want to spring for,
>a load-balancing
>appliance. I *may*, to start, just let VM handle that.
><snip>
>Thanks.
>
> mark
>
>--
>redhat-list mailing list
>unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
>https://www.redhat.com/mailman/listinfo/redhat-list
>
More information about the redhat-list
mailing list