Skip to content
This repository was archived by the owner on Feb 24, 2026. It is now read-only.

Docs: Update gapic upgrade installation instructions #1677

Merged
cindy-peng merged 5 commits into from
Dec 5, 2024
Merged

Docs: Update gapic upgrade installation instructions #1677

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
8b8abac
Update user guide
cindy-peng Dec 4, 2024
3789d13
chore: generate libraries at Wed Dec 4 18:25:42 UTC 2024
cloud-java-bot Dec 4, 2024
af4f291
Formatting code block
cindy-peng Dec 4, 2024
7faf05a
chore: generate libraries at Wed Dec 4 19:22:29 UTC 2024
cloud-java-bot Dec 4, 2024
43b3a2c
Remove client-side metrics suggestions
cindy-peng Dec 4, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Remove client-side metrics suggestions
  • Loading branch information
@cindy-peng
cindy-peng committed Dec 4, 2024
commit 43b3a2c0e68a91dde66693f16d0f92dba789cccd
4 changes: 2 additions & 2 deletions .readme-partials.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -194,9 +194,9 @@ custom_content: |

However sometimes you may want to change your connection pool size due to high throughput or buffered requests. Ideally, to leave room for traffic fluctuations, a connection pool has about twice the number of connections it takes for maximum saturation. Because a connection can handle a maximum of 100 concurrent requests, between 10 and 50 outstanding requests per connection is optimal. The limit of 100 concurrent streams per gRPC connection is enforced in Google's middleware layer, and you are not able to reconfigure this number.

The following steps help you calculate the optimal number of connections in your channel pool using client-side metrics.
The following steps help you calculate the optimal number of connections in your channel pool using estimate per-client QPS and average latency numbers.

From your client-side metrics, gather the following information:
To calculate the optimal connections, gather the following information:

1. The maximum number of queries per second (QPS) per client when your application is running a typical workload.
2. The average latency (the response time for a single request) in ms.
Expand Down
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -292,9 +292,9 @@ The default connection pool size is right for most applications, and in most cas

However sometimes you may want to change your connection pool size due to high throughput or buffered requests. Ideally, to leave room for traffic fluctuations, a connection pool has about twice the number of connections it takes for maximum saturation. Because a connection can handle a maximum of 100 concurrent requests, between 10 and 50 outstanding requests per connection is optimal. The limit of 100 concurrent streams per gRPC connection is enforced in Google's middleware layer, and you are not able to reconfigure this number.

The following steps help you calculate the optimal number of connections in your channel pool using client-side metrics.
The following steps help you calculate the optimal number of connections in your channel pool using estimate per-client QPS and average latency numbers.

From your client-side metrics, gather the following information:
To calculate the optimal connections, gather the following information:

1. The maximum number of queries per second (QPS) per client when your application is running a typical workload.
2. The average latency (the response time for a single request) in ms.
Expand Down