pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedRegarding server sizing for postgres database
2+ messages / 2 participants
[nested] [flat]
* Regarding server sizing for postgres database
@ 2014-05-17 05:20 Ramkumar Raghavan <ramkumar.raghavan@gmail.com>
2014-05-19 22:37 ` Re: Regarding server sizing for postgres database Steve Crawford <scrawford@pinpointresearch.com>
0 siblings, 1 reply; 2+ messages in thread
From: Ramkumar Raghavan @ 2014-05-17 05:20 UTC (permalink / raw)
To: pgsql-admin
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.
Thanks
Ramkumar
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Regarding server sizing for postgres database
2014-05-17 05:20 Regarding server sizing for postgres database Ramkumar Raghavan <ramkumar.raghavan@gmail.com>
@ 2014-05-19 22:37 ` Steve Crawford <scrawford@pinpointresearch.com>
0 siblings, 0 replies; 2+ messages in thread
From: Steve Crawford @ 2014-05-19 22:37 UTC (permalink / raw)
To: Ramkumar Raghavan <ramkumar.raghavan@gmail.com>; pgsql-admin
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
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2014-05-19 22:37 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2014-05-17 05:20 Regarding server sizing for postgres database Ramkumar Raghavan <ramkumar.raghavan@gmail.com>
2014-05-19 22:37 ` Steve Crawford <scrawford@pinpointresearch.com>
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