sizing / capacity planning tipps related to expected request or transactions per second

From: Dirk Krautschick <Dirk(dot)Krautschick(at)trivadis(dot)com>
To: "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org>
Subject: sizing / capacity planning tipps related to expected request or transactions per second
Date: 2020-08-24 16:39:46
Message-ID: AM0PR05MB6082A57CCA80CBFFC16F08A1E9560@AM0PR05MB6082.eurprd05.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Hi,

are there any nice rules of thumb about capacity planning in relation the expected
amount of transactions or request per second?

For example, if I have around 100 000 transactions per second on a 5 TB database.
With what amount of Memory and CPUs/Cores and which settings would you basically
Start to evaluate the performance.

Or are there any other recommendations or experiences here?

Thanks and best regards

Dirk

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message MichaelDBA 2020-08-24 16:49:21 Re: sizing / capacity planning tipps related to expected request or transactions per second
Previous Message Jim Jarvie 2020-08-21 15:24:20 Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED