You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How is this benchmark valid if the port is randomly generated and only retrievable via a log? It seems like you should bench port 8080 since that's what would need to be used in reality. It would also be nice if these benchmarks included the steps to reproduce.
In my tests with Encore.ts I get 44k req/s with the regular API, 4k req/s with the raw API (how is this 10x worse?), compared to 260k with Elysia & Bun, and 150k with Hono and Bun.
As you can see from these results Encore is one of the worse performing frameworks one could pick. The instructions here are useless because I could not actually use that random port in prouction.
The text was updated successfully, but these errors were encountered:
How is this benchmark valid if the port is randomly generated and only retrievable via a log? It seems like you should bench port 8080 since that's what would need to be used in reality. It would also be nice if these benchmarks included the steps to reproduce.
In my tests with Encore.ts I get 44k req/s with the regular API, 4k req/s with the raw API (how is this 10x worse?), compared to 260k with Elysia & Bun, and 150k with Hono and Bun.
I did my test on my MacBook Pro with Docker maybe the arm64 or Docker has something to do with it? Here's what I did https://github.com/Gobd/nodebench/blob/main/runtimes/encore/build.sh then ran the test using Bombardier against port 8080 from another Docker container using a Compose file.
As you can see from these results Encore is one of the worse performing frameworks one could pick. The instructions here are useless because I could not actually use that random port in prouction.
The text was updated successfully, but these errors were encountered: