Skip to content
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 occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate TCP connection for each virtual user #334

Closed
ghost opened this issue Sep 10, 2015 · 2 comments
Closed

Separate TCP connection for each virtual user #334

ghost opened this issue Sep 10, 2015 · 2 comments

Comments

@ghost
Copy link

ghost commented Sep 10, 2015

I think each virtual user should have it's own TCP connection by default, but we should be able to specify whether we'd like to share connections.

@cgoldberg
Copy link
Member

AFAICT, each VU does use it's own TCP connection. Where in the code do you see otherwise?
Why would you ever want to share TCP connections between VU's? That makes no sense to me.

@ghost
Copy link
Author

ghost commented Oct 20, 2015

If think I remember urlib3 connection pools, I could do a TCP count when running a sample test, but I don't use Locust anymore as I moved to Gatling. So I'll close it.

This issue was closed.
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

No branches or pull requests

1 participant