feat: Use multiplexed sessions for read-only transactions #3917
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Warning: This pull request is touching the following templated files:
|
9c195b1 to
6298992
Compare
rahul2393
previously approved these changes
Jun 19, 2025
|
Couple of suggestions - Please ignore if any of these points have already been addressed.
|
|
@harshachinta Thanks for your inputs.
|
olavloite
approved these changes
Jun 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Multi-use and single-use read-only transactions now use a single multiplexed session, instead of a session from the session pool. Multiplexed sessions can handle any number of queries and read-only transactions at the same time.
This change means that the client library will require fewer regular sessions to run the same workload. How much, depends on the distribution of read-only vs read/write transactions that are executed by the application.
Users do not need to take any specific action to re-configure their Spanner client due to this change. However, users who have configured a large number of Min or Max sessions in the session pool due to executing a large number of read-only transactions, could consider whether they can lower this number.
This change does not affect how read/write transactions are executed.
The use of multiplexed sessions can be disabled by setting the environment variable GOOGLE_CLOUD_SPANNER_MULTIPLEXED_SESSIONS=false.
See https://cloud.google.com/spanner/docs/sessions#multiplexed_sessions for more background information about multiplexed sessions.