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
{{ message }}
This repository has been archived by the owner on Mar 16, 2022. It is now read-only.
Then the test http application listening on port 8001:
varhttp=require('http');varserver=http.createServer(function(req,res){res.writeHead(200);res.end('hey');}).listen(process.env.PORT||8001,function(){console.log('App listening on port 8001');});
I did a benchmark with wrk. The first one without rocky and the second by hitting rocky for traffic balancing:
The result is quite different with and without rocky.
Without rocky (builting node http server) I get 246000 requests processed in 10 seconds. By using rocky It goes to 14997 requests in 10 seconds, 16x less performant than the raw http server.
Do you have any tips on enhancing overall performance?
Aside from performance, rocky is clearly robust!
Thanks
The text was updated successfully, but these errors were encountered:
Hello h2non,
I'm trying to use rocky as a loadbalancer, before digging into using http middlewares for traffic replay.
I did a benchmark before going further with this code:
Then the test http application listening on port 8001:
I did a benchmark with wrk. The first one without rocky and the second by hitting rocky for traffic balancing:
The result is quite different with and without rocky.
Without rocky (builting node http server) I get 246000 requests processed in 10 seconds. By using rocky It goes to 14997 requests in 10 seconds, 16x less performant than the raw http server.
Do you have any tips on enhancing overall performance?
Aside from performance, rocky is clearly robust!
Thanks
The text was updated successfully, but these errors were encountered: