8000 Avoid warmup grpc connection multiple times by ktalg · Pull Request #926 · fortio/fortio · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Avoid warmup grpc connection multiple times #926

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasional 8000 ly send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 31, 2024
Merged

Conversation

ktalg
Copy link
Collaborator
@ktalg ktalg commented May 30, 2024

Currently, each new grpc connection is used to send multiple warmup requests (when grpc-stream>0), which is unexpected, especially for scenarios where the server takes a long time to process, and the whole warmup process will consume a lot of time.

@ktalg ktalg requested a review from ldemailly May 30, 2024 03:11
@ldemailly
Copy link
Member

Thanks - I find it surprising that warming only the first stream of each multiplexed connections makes a difference, specially with the ping 8000 server itself, is that what you see?

@ldemailly
Copy link
Member

can you add also the nolint so gocyclo / ci passes?

@ktalg
Copy link
Collaborator Author
ktalg commented May 31, 2024

Thanks - I find it surprising that warming only the first stream of each multiplexed connections makes a difference, specially with the ping server itself, is that what you see?

In a testing scenario where the client and server are far apart, each request takes 50ms to reach its destination. When conducting the test: fortio load -grpc -ping -c=10 -s=100 -qps=0 -H="host: server" -gomaxprocs=2 -t=30s <server addr>, fortio requires 10x100x50=50000ms=50s for warmup! This time cost is even greater than the duration of the test itself, which seems unreasonable. I believe that warming up each connection only once should suffice, as this would not cause any adverse effects.

Copy link
Member
@ldemailly ldemailly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks !

@ldemailly ldemailly merged commit 854b9ce into fortio:master May 31, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0