Yes, it’s possible that you might encounter scaling issues with Airbyte when running over a thousand connections. As a reference point, the typical Airbyte user has 5 - 20 connectors and 10 - 100 connections configured. Almost all of these connections are scheduled, either hourly or daily, resulting in at most 100 concurrent jobs. If you have a larger workload, you might need to consider scaling your Airbyte deployment (source). However, the performance of each connector also depends on the connector configuration and the API you’re trying to replicate. Changing the worker configuration in the .env file will only increase/decrease the number of parallel syncs you’ll run (source). If you’re experiencing performance issues, it might be worth checking if there are any specific limitations with the connectors you’re using. For example, the Notion connector is restricted by Notion’s request limits (source). If you’re still facing issues, consider reaching out to the Airbyte community on their forum or Slack channel for further assistance.