Jira (PDB-5167) Obtain performance information for Estate Reporting

0 views
Skip to first unread message

Bogdan Irimie (Jira)

unread,
Jun 30, 2021, 3:52:02 AM6/30/21
to puppe...@googlegroups.com
Bogdan Irimie created an issue
 
PuppetDB / Task PDB-5167
Obtain performance information for Estate Reporting
Issue Type: Task Task
Assignee: Unassigned
Created: 2021/06/30 12:51 AM
Priority: Normal Normal
Reporter: Bogdan Irimie
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Atlassian logo

Bogdan Irimie (Jira)

unread,
Jun 30, 2021, 3:53:03 AM6/30/21
to puppe...@googlegroups.com

Bogdan Irimie (Jira)

unread,
Jun 30, 2021, 3:55:02 AM6/30/21
to puppe...@googlegroups.com
Bogdan Irimie updated an issue
Change By: Bogdan Irimie
Sprint: ghost-14.07.2021

Bogdan Irimie (Jira)

unread,
Jun 30, 2021, 3:56:02 AM6/30/21
to puppe...@googlegroups.com
Bogdan Irimie updated an issue
* generate results for 10 000 up to 500 000 nodes and identify slow queries  or possible errors. Initially we should use n1/n2 servers and if they can't handle the load consider using EC2 instances form AWS.
* The deployment will be composed of 1 postgresql and 1 PDB. if PDB becomes a bottleneck, we should scale to multiple PDB and add a load balancer in front of them. If PostgreSql becomes the bottleneck we should:
** identify the queries that are slow
** scale PostgreSQL horizontally
** tweak PostgreSQL settings or PDB settings

Bogdan Irimie (Jira)

unread,
Jun 30, 2021, 3:59:02 AM6/30/21
to puppe...@googlegroups.com
Bogdan Irimie updated an issue
* generate results for 10 000 up to 500 000 nodes and identify slow queries  or possible errors. Initially we should use n1/n2 servers and if they can't handle the load consider using EC2 instances form AWS.
* (optional, might require another ticket) The deployment will be composed of 1 postgresql and 1 PDB. if PDB becomes a bottleneck, we should scale to multiple PDB and add a load balancer in front of them. If PostgreSql becomes the bottleneck we should:

** identify the queries that are slow
** scale PostgreSQL horizontally
** tweak PostgreSQL settings or PDB settings

Bogdan Irimie (Jira)

unread,
Jun 30, 2021, 4:04:02 AM6/30/21
to puppe...@googlegroups.com
Bogdan Irimie updated an issue
Change By: Bogdan Irimie
Sprint: ghost-14.07.2021

Bogdan Irimie (Jira)

unread,
Jun 30, 2021, 4:08:01 AM6/30/21
to puppe...@googlegroups.com

Bogdan Irimie (Jira)

unread,
Jun 30, 2021, 4:11:01 AM6/30/21
to puppe...@googlegroups.com

Andrei Filipovici (Jira)

unread,
Jul 13, 2021, 6:54:02 AM7/13/21
to puppe...@googlegroups.com

Oana Tanasoiu (Jira)

unread,
Jul 15, 2021, 3:20:03 AM7/15/21
to puppe...@googlegroups.com

Bogdan Irimie (Jira)

unread,
Jul 20, 2021, 3:23:04 AM7/20/21
to puppe...@googlegroups.com
Bogdan Irimie updated an issue
Change By: Bogdan Irimie
* generate results for 10 000 up to 500 100 000 nodes and identify slow queries  or possible errors. Initially we should use n1/n2 servers and if they can't handle the load consider using EC2 instances form AWS.
* (optional, might require another ticket)The deployment will be composed of 1 postgresql and 1 PDB. if PDB becomes a bottleneck, we should scale to multiple PDB and add a load balancer in front of them. If PostgreSql becomes the bottleneck we should:

** identify the queries that are slow
** scale PostgreSQL horizontally
** tweak PostgreSQL settings or PDB settings

Bogdan Irimie (Jira)

unread,
Jul 20, 2021, 3:24:02 AM7/20/21
to puppe...@googlegroups.com
Bogdan Irimie updated an issue
Change By: Bogdan Irimie
Sprint: ghost-28.07.2021

Andrei Filipovici (Jira)

unread,
Jul 20, 2021, 7:16:04 AM7/20/21
to puppe...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages