Also 4. If I configured multiple sync which are scheduled to run at the same time and each sync is trying to pull more than a million records, how many concurrent syncs are allowed?

The number of concurrent syncs that Airbyte can run depends on the source and destination connectors you are using and the configuration of your Airbyte instance. For instance, when using the Mailchimp source connector, Mailchimp enforces a maximum of 10 simultaneous connections to its API, which means that Airbyte is unable to run more than 10 concurrent syncs from Mailchimp using API keys generated from the same account [source](https://docs.airbyte.com/integrations/sources/mailchimp). On the other hand, when using the Cumul.io destination connector, having more than 200 concurrent Airbyte connections flushing the data simultaneously might run into Cumul.io's API Rate limit. As a workaround, it is recommended to use separate API key and tokens for identical destination connectors in case you would expect such concurrency [source](https://docs.airbyte.com/integrations/destinations/cumulio). If you are deploying Airbyte on Kubernetes, the number of concurrent syncs also depends on the number of pods you have configured. Airbyte creates a pod for each connection, so if you have configured 200 concurrent connections, Airbyte will create 200 pods [source](https://airbytehq.slack.com/archives/C021JANJ6TY/p1677790475205889). Please note that running multiple concurrent syncs, especially with large volumes of data, can impact the performance of your Airbyte instance and the systems you are connecting to. It's recommended to monitor the performance and adjust your configuration as needed.