-
Notifications
You must be signed in to change notification settings - Fork 67
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
opium in techempower frameworks benchmarks #207
Comments
Hi @mudrz, That's awesome, thanks a lot for doing this! I'm very curious to see how the next version of Opium (w/ Httpaf) will compare with the one you used for the benchmarks (w/ Cohttp). The benchmarks showing a better performance of Httpaf compared to Cohttp are at least 3 years old and Cohttp evolved a lot since then, so I wonder if they still stand. |
in the current implementation opium is pinned to a master commit with httpaf but it's really easy to add a new dockerfile and use the cohttp version in order to compare |
edit: didn't notice that the httpaf version has a new API, so it's it would need more work to create a benchmark with cohttp; also there are now results: @tmattio poster about the results here: There is something wrong with the plaintext results, not sure if it is in my implementation, or perhaps there's something in opium? |
Hi @mudrz, There's definitely something going on with the plain text serialization. I'll look into it as soon as I have some spare time! Thanks again for doing this, it's great to see where Opium positions itself in comparison with other frameworks 🙂 |
the (but there doesn't seem to be a new release) |
not really an issue, but just letting you know that opium was added to the techempower frameworks benchmarks
https://github.com/TechEmpower/FrameworkBenchmarks/tree/master/frameworks/OCaml/opium
it didn't catch the last benchmarks run until a planned update of their tools TechEmpower/FrameworkBenchmarks#6064
so the next benchmarks run will be delayed indefinitely
in the meantime please feel free to make changes and improvements
The text was updated successfully, but these errors were encountered: