-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
What is the most serious performance problem? #17
Comments
The HTTP parser does a bunch of things that you shouldn't do if you care about performance. A large number of which are in the Pony Performance Cheatsheet as "don't do's". That's where you would want to start. The existing parser uses |
It also uses buffered.Reader to parse http payloads spanning > 1 tcp packet. In this process it copies all the bytes of the payload. I already have a few ideas on how to tackle those problems. |
@SeanTAllen @mfelsche |
you're welcome @toyoaki-k |
In RFC 55, this http server seems to have perfomance problem as a http server
What is the most serious performance problem?
I think this sever creates one actor per one connection. I think that way is good for perfomance in terms of concurrent process of connections.
The text was updated successfully, but these errors were encountered: