feat(source-gitlab): Increase default concurrency from 8 to 10 (4.4.23-rc.3)#75537
Conversation
…3-rc.3) Co-Authored-By: sophie.cui@airbyte.io <sophie.cui@airbyte.io>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
|
Note 📝 PR Converted to Draft More info...Thank you for creating this PR. As a policy to protect our engineers' time, Airbyte requires all PRs to be created first in draft status. Your PR has been automatically converted to draft status in respect for this policy. As soon as your PR is ready for formal review, you can proceed to convert the PR to "ready for review" status by clicking the "Ready for review" button at the bottom of the PR page. To skip draft status in future PRs, please include |
Co-Authored-By: sophie.cui@airbyte.io <sophie.cui@airbyte.io>
👋 Greetings, Airbyte Team Member!Here are some helpful tips and reminders for your convenience. 💡 Show Tips and TricksPR Slash CommandsAirbyte Maintainers (that's you!) can execute the following slash commands on your PR:
📚 Show Repo GuidanceHelpful Resources
|
|
Deploy preview for airbyte-docs ready! ✅ Preview Built with commit d879a79. |
|
What
Increases the default concurrency level for source-gitlab from 8 to 10 as the next step in the progressive rollout concurrency tuning process (epic).
RC.2 (which commented out HTTPAPIBudget) showed stable or slightly improved performance vs RC.1 across all pinned actors with zero failures. This RC bumps concurrency to measure the effect of higher parallelism without rate limiting.
How
manifest.yaml: Changedefault_concurrencyfallback from8to10(users who setnum_workersin config are unaffected)metadata.yaml: BumpdockerImageTagfrom4.4.23-rc.2to4.4.23-rc.3gitlab.md: Add changelog entryReview guide
manifest.yaml— single-line concurrency default changemetadata.yaml— version bumpdocs/integrations/sources/gitlab.md— changelog entry (75535matches this PR's actual number)User Impact
No immediate user impact — this RC will only be deployed to ~15 pinned actors via progressive rollout. Users who have explicitly configured
num_workersare unaffected. If the concurrency increase causes issues (rate limiting, failures), it will be caught during rollout monitoring before wider release.Can this PR be safely reverted and rolled back?
Link to Devin session: https://app.devin.ai/sessions/4462c8953c3c483084a62a7240f6973f
Requested by: sophiecuiy