source-salesforce: performance tuning

[David Gold (dbgold17)]

What

Per a discussion with Maxime Carbonneau-Leclerc (@maxi297), we believe increasing the maximum number of workers and maximum number of concurrent async jobs will speed up connector performance, especially for larger syncs.

An added benefit of making this change is it should allow us to test out the ability of the new connector performance dashboard to measure the impact.

EDIT (max): I've also added the normalization performance improvements as part of this PR. This should address https://github.com/airbytehq/oncall/issues/9850

Can this PR be safely reverted and rolled back?

• YES 💚
• NO ❌

[github-actions]

👋 Greetings, Airbyte Team Member!

Here are some helpful tips and reminders for your convenience.

Helpful Resources

• Developing Connectors Locally
• Managing Connector Secrets
• On-Demand Live Tests
• On-Demand Regression Tests
• #connector-ci-issues
• #connector-publish-updates
• #connector-build-statuses

PR Slash Commands

Airbyte Maintainers (that's you!) can execute the following slash commands on your PR:

• /format-fix - Fixes most formatting issues.
• /update-connector-cdk-version connector=<CONNECTOR_NAME> - Updates the specified connector to the latest CDK version.
  Example: /update-connector-cdk-version connector=destination-bigquery
• /bump-version - Bumps connector versions.
  • You can specify a custom changelog by passing changelog. Example: /bump-version changelog="My cool update"
  • Leaving the changelog arg blank will auto-populate the changelog from the PR title.
• /run-cat-tests - Runs legacy CAT tests (Connector Acceptance Tests)
• /build-connector-images - Builds and publishes a pre-release docker image for the modified connector(s).
• /poe connector source-example lock - Run the Poe lock task on the source-example connector, committing the results back to the branch.
• /poe source example lock - Alias for /poe connector source-example lock.
• /poe source example use-cdk-branch my/branch - Pin the source-example CDK reference to the branch name specified.
• /poe source example use-cdk-latest - Update the source-example CDK dependency to the latest available version.

📝 Edit this welcome message.

[David Gold (dbgold17)]

/bump-version changelog="Minor tuning to increase sync speed."

Bump Version job started... Check job output.

🔴 Job completed successfully (no changes, this is sus).

[github-actions]

source-salesforce Connector Test Results

100 tests   96 ✅  17s ⏱️
  2 suites   4 💤
  2 files     0 ❌

Results for commit d70c8f8.

♻️ This comment has been updated with latest results.

[Maxime Carbonneau-Leclerc (maxi297)]

Have we run regression test on this? Do we want to pin some versions on connections we know might have a speed boost from this?

[github-actions]

Deploy preview for airbyte-docs ready!

✅ Preview
https://airbyte-docs-eh6lad0py-airbyte-growth.vercel.app

Built with commit d70c8f8.
This pull request is being automatically deployed with vercel-action

[David Gold (dbgold17)]

Maxime Carbonneau-Leclerc (@maxi297) thanks for the reminders

regression test run here: https://github.com/airbytehq/airbyte/actions/runs/18328555364

potential connections to pin:

• https://cloud.airbyte.com/workspaces/287a6b3c-ced2-4af6-a495-181de5437a25/connections/248477bd-801d-4432-8dde-6cbc986989ab/timeline?jobId=52535256&attemptNumber=0
• https://cloud.airbyte.com/workspaces/6c223e2d-e9e6-4e7f-a122-1c9187a17be3/connections/178bf4a2-4d76-4b47-a0b6-fa4de5736ee6/timeline?jobId=52545378&attemptNumber=0

[Maxime Carbonneau-Leclerc (maxi297)]

It seems like regression testing is hitting the same problem Brian Lai (@brianjlai) had. Can we run the regression testing with specific connections? I'll have a look into this issue tomorrow

[Maxime Carbonneau-Leclerc (maxi297)]

See https://airbytehq-team.slack.com/archives/C02UJ11D3S6/p1759936631631699 for more details about the regression tests failure. In the meanwhile, can we re-run regression tests with a couple of specific connections?

[David Gold (dbgold17)]

new approach. I plan to publish a pre-release (dev) version and pin some connections.

Pre-release publish workflow: https://github.com/airbytehq/airbyte/actions/runs/18381278400

[Maxime Carbonneau-Leclerc (maxi297)]

Waiting for a confirmation from David Gold (@dbgold17) but I would start the rollout next Monday

[David Gold (dbgold17)]

🚢 it

[Maxime Carbonneau-Leclerc (maxi297)]

Regression tests: https://github.com/airbytehq/airbyte/actions/runs/18820177051

EDIT: Issue with byos. Gonna use https://github.com/airbytehq/airbyte/actions/runs/18820761165

[Maxime Carbonneau-Leclerc (maxi297)]

https://github.com/airbytehq/airbyte-platform-internal/pull/18170 has been merged. Retriggering regression tests on https://github.com/airbytehq/airbyte/actions/runs/18849208256

[Maxime Carbonneau-Leclerc (maxi297)]

Regression tests did not run because it can't find connections. In the meanwhile, I've tested pinning versions for a couple of users and everything seemed fine. I'll move forward with the progressive rollout and investigate the regression test issue later today