Message-ID: <537A87B1.6090308@pinpointresearch.com>
Date: Mon, 19 May 2014 15:37:37 -0700
From: Steve Crawford <scrawford@pinpointresearch.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Ramkumar Raghavan <ramkumar.raghavan@gmail.com>,
 pgsql-admin@postgresql.org
Subject: Re: Regarding server sizing for postgres database
References: 
 <CAHSJah9U9SFQD292GedmAidNV2EQCLCiAhb3e7-qs3Wvag3F0w@mail.gmail.com>
In-Reply-To: 
 <CAHSJah9U9SFQD292GedmAidNV2EQCLCiAhb3e7-qs3Wvag3F0w@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

On 05/16/2014 10:20 PM, Ramkumar Raghavan wrote:
> Hi,
>
>   I need to decide the server hardware configuration for the postgres 
> database.
>
> I have the following information for sizing:
>
> concurrent users: 100
>
> Total data traferred throughout a day to the database: 10GB
>
> Total database storage size required: 3TB
>
> I am planning to virtualize it using vmware ESXi.
>
> Please let me know if 10 core, 64bit Intel CPU, 24GB RAM sufficient 
> for the above requirements.
>
>
Who knows?

100 mostly idle users doing small optimized selects is a far cry from 80 
users with rapid response requirements doing a constant heavy stream of 
inserts and updates to tables with multiple indexes and foreign-key 
constraints while the other 20 are doing large reporting and analytics 
queries. Both use-cases match the above description.

To get a useful answer you will need to provide lots more detail about 
the nature of the workload and expected responsiveness.

Cheers,
Steve


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin