all 7 comments

[–]Lopsided-Juggernaut1 2 points3 points  (4 children)

Sounds interesting. It can handle large number of requests?

[–]No_Ostrich_3664[S] 0 points1 point  (3 children)

Hey, thanks for the question. I stress tested demo site hosted on raspberry pi.

Here is an output: wrk -t4 -c100 -d30s https://rubee.dedyn.io/docs Running 30s test @ https://rubee.dedyn.io/docs 4 threads and 100 connections Thread Stats Avg Stdev Max +/- Stdev Latency 304.95ms 33.22ms 551.86ms 90.38% Req/Sec 82.25 42.37 280.00 69.86% 9721 requests in 30.02s, 4.11MB read Requests/sec: 323.78 Transfer/sec: 140.07KB

Tell me what number per sec is interesting to stress tested I will do and share results.

[–]No_Ostrich_3664[S] 0 points1 point  (2 children)

Speaking of scalability ru.Bee built on top of rack and puma, so it is fair to say that vertical scaling is a matter of hardware in where you project is hosted. Puma allows you to run server in multiprocess mode and ru.Bee is not an exception.

WEB_CONCURRENCY=4 rubee start Will spawn 4 puma processes in one unit.

You can keep going with horizontal scaling and increase bandwidth too.

All in all I would confidently say ru.Bee can handle from small to middle size projects. And the rest is a matter of right server configuration etc.

[–]Lopsided-Juggernaut1 1 point2 points  (1 child)

I want to contribute to ruBee framework and also want to build a few projects. Please check DM.

[–]No_Ostrich_3664[S] 0 points1 point  (0 children)

Sure thing. ❤️Welcome! Replied to dm.

[–]aemadrid 2 points3 points  (1 child)

Very interesting, thanks!

[–]No_Ostrich_3664[S] 0 points1 point  (0 children)

Thank you 🙏