Capacity Planning
Some of the aspects you may want to consider are:
1) Per unit time (day or week), how much data will be persisted to the
database, number of records and total size of the data.
2) How much of these data will be updated and how frequently in a given
time unit (day or week).
3) Will the databases hosted on the server be for OLTP (OnLine
Transactional Processing) or OLAP (OnLine Analytical Processing) or a
combination of the two.
4) In case of hardware failure or electrical outage or outage due to other
factors including human activity, how much loss of data (and time) can be
tolerated, see "https://www.postgresql.org/docs/11/backup.html" and "
https://www.postgresql.org/docs/11/high-availability.html".
5) The size of the budget for hardware and manpower.
Allan.
On Sat, Jan 19, 2019 at 1:38 PM bhargav kamineni <kbn98406@gmail.com> wrote:
Show quoted text
Hi Team,
What are the check lists for doing capacity planning for a postgresql
server ?Regards,
BK.
IOW, the same as every other RDBMS...
On 1/20/19 1:29 AM, Allan Kamau wrote:
Some of the aspects you may want to consider are:
1) Per unit time (day or week), how much data will be persisted to the
database, number of records and total size of the data.
2) How much of these data will be updated and how frequently in a given
time unit (day or week).
3) Will the databases hosted on the server be for OLTP (OnLine
Transactional Processing) or OLAP (OnLine Analytical Processing) or a
combination of the two.
4) In case of hardware failure or electrical outage or outage due to other
factors including human activity, how much loss of data (and time) can be
tolerated, see "https://www.postgresql.org/docs/11/backup.html" and
"https://www.postgresql.org/docs/11/high-availability.html".
5) The size of the budget for hardware and manpower.Allan.
On Sat, Jan 19, 2019 at 1:38 PM bhargav kamineni <kbn98406@gmail.com
<mailto:kbn98406@gmail.com>> wrote:Hi Team,
What are the check lists for doing capacity planning for a postgresql
server ?Regards,
BK.
--
Angular momentum makes the world go 'round.
Thank-you Allan.
On Sun, Jan 20, 2019 at 1:59 PM Ron <ronljohnsonjr@gmail.com> wrote:
Show quoted text
IOW, the same as every other RDBMS...
On 1/20/19 1:29 AM, Allan Kamau wrote:
Some of the aspects you may want to consider are:
1) Per unit time (day or week), how much data will be persisted to the
database, number of records and total size of the data.
2) How much of these data will be updated and how frequently in a given
time unit (day or week).
3) Will the databases hosted on the server be for OLTP (OnLine
Transactional Processing) or OLAP (OnLine Analytical Processing) or a
combination of the two.
4) In case of hardware failure or electrical outage or outage due to other
factors including human activity, how much loss of data (and time) can be
tolerated, see "https://www.postgresql.org/docs/11/backup.html" and "
https://www.postgresql.org/docs/11/high-availability.html".
5) The size of the budget for hardware and manpower.Allan.
On Sat, Jan 19, 2019 at 1:38 PM bhargav kamineni <kbn98406@gmail.com>
wrote:Hi Team,
What are the check lists for doing capacity planning for a postgresql
server ?Regards,
BK.--
Angular momentum makes the world go 'round.