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

Running out of local connections in reqstatsrv example #3

Open
dhontecillas opened this issue Mar 17, 2021 · 0 comments
Open

Running out of local connections in reqstatsrv example #3

dhontecillas opened this issue Mar 17, 2021 · 0 comments

Comments

@dhontecillas
Copy link
Owner

For the reqstatsrv example: lotsofconnection , the test running out of local sockets to create connections against the backend server:

error proxying the request: Get "http://192.168.1.20:9876/endpoint_9": dial tcp 192.168.1.20:9876: connect: cannot assign requested address
error proxying the request: Get "http://192.168.1.20:9876/endpoint_39": dial tcp 192.168.1.20:9876: connect: cannot assign requested address
error proxying the request: Get "http://192.168.1.20:9876/endpoint_39": dial tcp 192.168.1.20:9876: connect: cannot assign 

The dummy reqstatsrv does not support the keep-alive options, so connections cannot be reused, and we hit a number of maximum parallel requests. Also , the loadimpact/k6 script is also using local connections, so when running the test in a local machine we can only handle half of the requests.

Profiling the code, it was found that it was the actual cpu bottleneck:

2021-03-17-194502_652x403_scrot

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