-
Notifications
You must be signed in to change notification settings - Fork 103
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
Server crashes when using glommio #204
Comments
do you have backtrace or error? |
Could it be because of the HttpClient that carry an |
It is on the there! |
Well it should be the same for tokio multi threaded? In tokio it does not crash, just in glommio. So what do you recommend, just arc the client and add it to the app state? |
Also forgot to mention, the server crash during load testing. I was load testing both runtimes to see if there is any difference. Tokio does not crash. Glommio crash when i do more than 50 request/second. So i don't think it is Rc issue. |
do you have backtrace for crash? |
oh, right |
could you try this "glommio-borrow-fix" branch |
Thank you! I will try tomorrow and let you know. |
It seems like the fix helped a bit, the server now is accepting more requests but still eventually crash when i do perf load 100 request/second. I have made some changes to the code, I moved the http client that makes the external request to the app state.
Cargo.toml:
I'm using vegeta for load testing: The server panics:
|
are you sure you use right branch? your last backtrace points to old code |
I mean i'm using: |
I just double checked and cleaned and rerun, same error. Not sure why it is pointing to the old code. |
i think you need to override ntex-glommio only |
Can you please elaborate more? |
you need this entry to cargo.toml
|
I did:
It is not panicking anymore!! It looks like that was the fix! |
fixed in master |
Last question, what is the difference between using Which should I use? |
features = ["glommio"], ntex-glommio does not exists |
Hi,
I'm prototyping a service, decided to try out ntex. I stripped out irrelevant logic kept the logic that is triggering the crash. Im using vegeta to load test the server using tokio and glommio runtimes. With tokio runtime it does not crash, with glommio it does after a certain threshold which again, it does not happen with tokio..
Logs:
The text was updated successfully, but these errors were encountered: