Hi! how to scale airbyte with postgress? what is the recommended db instance cpu, memory, # of pool connection?

To scale Airbyte with Postgres, you can adjust several parameters. One of the key parameters to adjust is the number of idle connections that Temporal maintains. By default, this value is

20

, but you may want to lower or increase this number based on your needs. Temporal creates multiple pools, and the number specified in the

SQL_MAX_IDLE_CONNS

environment variable of the

docker.compose.yaml

file might end up allowing 4-5 times more connections than expected. If you want to increase the amount of allowed idle connections, you will also need to increase

SQL_MAX_CONNS

as

SQL_MAX_IDLE_CONNS

is capped by

SQL_MAX_CONNS

[source](https://docs.airbyte.com/operator-guides/scaling-airbyte). As for the recommended DB instance CPU and memory, it largely depends on your specific use case and the scale of your operations. For instance, one user mentioned running Airbyte on an AWS EC2 instance (Linux) with 32 vCPUs and 128GB RAM for a MySQL DB table with about 200 million records [source](https://airbytehq.slack.com/archives/C021JANJ6TY/p1672748387444089). However, this might not be the optimal configuration for your specific use case. For more detailed information on scaling Airbyte, you can refer to the [Scaling Airbyte](https://docs.airbyte.com/operator-guides/scaling-airbyte) guide in the official documentation. If you encounter any issues or need further assistance, you can reach out to the Airbyte community on [Slack](https://airbytehq.slack.com/archives/C021JANJ6TY/p1672748387444089).