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
Investigate our performance on https://github.com/the-benchmarker/web-frameworks #1448
Comments
The Kitura implementation doesn't seem to include the NIO mode. May be we should add that too. |
David Jones and I investigated yesterday and he immediately noticed that Kitura is running inside an Ubuntu 14.04 Docker container, which is a performance penalty compared to running on 16.04 or 18.04 (related to an old + poorly performing libicu on that old distro) Unfortunately, our generated projects specify We can change to
after which we are ~35% faster. Here's a set of results which David ran locally (bare-metal Ubuntu 16.04 server, he modified the client/docker commands to run on 8 CPUs equivalent to the benchmark author's setup):
... we also don't see the regression between Kitura 2.6 and Kitura 2.7. They are about equal in performance. David has submitted a PR to update the Kitura dockerfiles to 18.04: At this point we're going to close off this issue and have raised two other separate issues covering two other items which we noticed whilst running this benchmark: |
FYI, I am working on running this on production-ready IaaS (instead of |
It has been reported in our Slack that we are not performing well when running this benchmark, in comparison to other Swift frameworks.
As we are not familiar with this benchmark we will take a look.
The text was updated successfully, but these errors were encountered: