From: Pascal Cohen <pcohen@wimba.com>
To: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: Hardware question for a DB server
Date: Fri, 14 Mar 2008 20:24:25 +0100
Message-ID: <47DAD0E9.2090500@wimba.com> (raw)
In-Reply-To: <Pine.GSO.4.64.0803121602410.28886@westnet.com>
References: <47D827EB.3020105@wimba.com>
<1205349821.9048.1128.camel@archimedes>
<Pine.GSO.4.64.0803121602410.28886@westnet.com>
Greg Smith wrote:
> On Wed, 12 Mar 2008, Mark Lewis wrote:
>
>> One question that's likely going to be important depending on your
>> answers above is whether or not you're getting a battery-backed write
>> cache for that ServeRAID-8K.
>
> Apparently there's a 8k-l and an regular 8-k; the l doesn't have the
> cache, so if this one is a regular 8-k it will have 256MB and a
> battery. See
> http://www.redbooks.ibm.com/abstracts/TIPS0054.html?Open#ServeRAID-8kIt is the solution with RAM and battery.
>
>> From Pascal's description of the application this system sounds like
> overkill whether or not there's a cache. For scaling to lots of small
> requests, using things like using connection pooling may end up being
> more important than worring about the disk system (the database isn't
> big enough relative to RAM for that to be too important).
>
I agree with what you are saying. We are using Java with a pool of
connections to access the DB. Today our database is really small
compared to the RAM but it may evolve and even will probably grow (hope
so which would be a good situation).
Thanks for your advices/remarks.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pcohen@wimba.com
Subject: Re: Hardware question for a DB server
In-Reply-To: <47DAD0E9.2090500@wimba.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox