Optimizing initial sync of Stripe Charges

Summary

The user is looking for ways to speed up the initial sync of Stripe Charges in Airbyte. They have provided details of their experience and referenced related GitHub issues. They suspect that optimizing the delegation of time slices across workers could help but are unsure where to start.


Question

Hello, has anyone here found ways to speed up an initial sync of Stripe Charges?

I’ve put more details about my experience here:
https://github.com/airbytehq/airbyte/issues/29575#issuecomment-2301210229

and I see there is a sort of unresolved issue about this here: https://github.com/airbytehq/airbyte/issues/18638

At first glance (read: I have only skimmed the connector source and am not familiar with how Airbyte delegates ingestion to workers etc), it seems like perhaps the delegation of the time slices across workers could be optimized but I’m not sure where to start looking to understand that better.



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["speed-up", "initial-sync", "stripe-charges", "optimization", "delegation", "workers", "airbyte"]

I also asked AI about this topic here - https://airbytehq.slack.com/archives/C01AHCD885S/p1724216310118299