* 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
* 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
* 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