I am wondering if anyone has had experience with t...
# replication-troubleshooting
k
I am wondering if anyone has had experience with the Google Ads connector and concurrency. It seems like the source connector is still limited by 1 CPU and is taking an extremely long time to import our large sources. I do see that the worker count is being sent and updated in the num_workers of the connectorConfig.json, but I also see that the var
Copy code
CONCURRENT_SOURCE_STREAM_READ:
false
. I am currently running the latest version of the connector 4.1.6 and running Airbyte OSS version 2.0.1 within a GKE cluster with autopilot. There are 4 cores available to each of the containers under the worker pod for this connection and the destination and orchestrator are barely taxed. I do notice that the connector is written in python, which may limit it to 1CPU, but I am unsure. Could I ask for community help on this? Thank you.