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

[D] Frameworks issues #6609

Closed
cyrusmsk opened this issue Aug 10, 2023 · 12 comments
Closed

[D] Frameworks issues #6609

cyrusmsk opened this issue Aug 10, 2023 · 12 comments

Comments

@cyrusmsk
Copy link
Contributor

Hi @waghanza

I've tried to run servers handy and serverino locally with the command:
wrk -H 'Connection: keep-alive' -d 5s -c 512 --timeout 8 -t 8 http://127.0.0.1:3000

They showed some values of requests, and still servers continue to work without any errors.
But I didn't use Dockers. Just run servers and wrk locally.
Can you get the error logs from your run or give any recommendations to test them locally?

@waghanza
Copy link
Collaborator

I'll investigate I have

wrk -H 'Connection: keep-alive' -d 5s -c 512 --timeout 8 -t 8 http://172.17.0.2:3000
Running 5s test @ http://172.17.0.2:3000
  8 threads and 512 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     0.00us    0.00us   0.00us    -nan%
    Req/Sec     0.00      0.00     0.00      -nan%
  0 requests in 5.06s, 0.00B read
Requests/sec:      0.00
Transfer/sec:       0.00B

Maybe Worker running as root. Is this intended? Set user/group from config to run worker as unprivileged user., I think we have to change the user on dockerfile

@cyrusmsk
Copy link
Contributor Author

Is it the picture for both Serverino and Handy?
Do you mean set user inside dockerfile?

@waghanza
Copy link
Collaborator

No only servernio. I'll work on this.

Yes, seems that the cause is docker. Not sure why, but there is no communication between docker and servernio

@cyrusmsk
Copy link
Contributor Author

Btw I've tried to run it in the docker locally. And it is working for me for both handy and serverino.
I used just simple Dockerfile. Build it and run with
docker run -d -p 3000:3000 image_name

@waghanza
Copy link
Collaborator

With handy the following command

wrk -H 'Connection: keep-alive' --connections 64 --threads 8 --duration 15 --timeout 1 --script /home/waghanza/workspace/benchmark/web/pipeline.lua http://172.17.0.2:3000

leads to

Running 15s test @ http://172.17.0.2:3000
  8 threads and 64 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency    27.59ms   42.32ms 489.95ms   86.06%
    Req/Sec   222.25    384.21     2.18k    90.00%
  24702 requests in 15.07s, 458.34KB read
  Socket errors: connect 0, read 24702, write 0, timeout 0
Requests/sec:   1638.88
Transfer/sec:     30.41KB

@cyrusmsk
Copy link
Contributor Author

It looks almost the same that I got locally on my laptop

@waghanza
Copy link
Collaborator

I have

★ [000008] [l] 2023-08-14 16:09 [connectionhandler.d:0315] Socket error on read. Resource temporarily unavailable

when running servernio on my laptop through docker

@waghanza
Copy link
Collaborator

@cyrusmsk
Copy link
Contributor Author

Hi. Did you change something in the run? Because now serverino is working.. but it is strange..

@waghanza
Copy link
Collaborator

Yes, strange.

I've only update the version

@cyrusmsk
Copy link
Contributor Author

Will close for now.
Maybe we can delete archttp - it looks abandoned and not working currently.

@waghanza
Copy link
Collaborator

Is archttp abandoned @zoujiaqing ?

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 a pull request may close this issue.

2 participants