Re: hardware requirements under Redhat

kbd wrote:
> Hello:
>
> I know that hardware requirements are dependent upon many factors.
> However I need a sanity check on this configuration.
>
> First the purpose of the database.
>   - database will be used to support a risk analysis group in a small
>     financial firm.
>   - there will be daily "bulk" loads to the database
>   - as well as updates via GUIs (JSP or java programs)
>   - initial size of the database will be 5Gig, could grow to 20 Gig quickly
>   - database will support daily batch reports and adhoc quieies/reports
>   - database is being designed with normalization and referential integrity
>       in mind.  Yes, we are going to think before we build.
>   - surrogate key will be used on the tables to reduce key size.
>        it is expected that this will reduce the size of primary
>        and foreign keys.
>
>
> I am considering a generic box with a single 2 - 2.6 Gig processor.
> 2 Gig of RAM and mirrored 200 Gig drives.
>
> Does this config cover the above requirements very well.
> Does anybody know if RedHat 9 or Fedora can address 2 Gig
> of RAM out of the box?
>
> many thanks
>
> kd

a.)I would start with a "server class" machine, ie. compaq DL380 or
comparable machine. You're saving money (alot) on your software.
You get builtin raid scsi, tons of reduntency, pre-engineered
server configuration and a three year warranty/support.

b.) I would then find what version of linux is supported
by the manufacture for thier equipment. ie. cpq I think is supporting
mostly redhat 7.3 / 8.0. (and others)

c.) Starting out with a good (hardware based) raid scsi setup will allow
a online migration path to different levels of raid or increasing
storage space as needed, etc. I always like to consider backup space as
well and diaster recovery too. ie. why start out with 200 gigs when your
needs are much smaller. Keeping your drives matched to your needs (as
small as possible) keeps costs/time down on backup/diaster recovery, ie.
I like to keep cloned copies of all my drives as backup, in a production
environment.

d.) Then you can always add (if needed), a second cpu, more memory, more
storage, more memory for cache controller etc.

e.) Also put some $ into clean power/cooling, if you haven't already.


If you're the person in charge of this production setup, tell'em
you won't sign off on the setup unless they put just a little money
into the hardware, put your foot down!

Ok, I feel better now,

I just get tried of people building white box
generic systems for a "production environment/criticial appilcation" and
then having strange problems and blaming the software and giving
open source software a bad rap.

Just my .02