sizing / capacity planning tipps related to expected request or transactions per second - Mailing list pgsql-performance

From Dirk Krautschick
Subject sizing / capacity planning tipps related to expected request or transactions per second
Date
Msg-id AM0PR05MB6082A57CCA80CBFFC16F08A1E9560@AM0PR05MB6082.eurprd05.prod.outlook.com
Whole thread Raw
Responses Re: sizing / capacity planning tipps related to expected request or transactions per second  (MichaelDBA <MichaelDBA@sqlexec.com>)
Re: sizing / capacity planning tipps related to expected request or transactions per second  (Pavel Stehule <pavel.stehule@gmail.com>)
List 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

pgsql-performance by date:

Previous
From: Jim Jarvie
Date:
Subject: Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED
Next
From: MichaelDBA
Date:
Subject: Re: sizing / capacity planning tipps related to expected request or transactions per second