New: Slimeweb -python#575
Conversation
|
Hey, thanks for submission. I'll check and fix your docker issues tommorow. |
|
Ty, This is my first time creating a docker file. Pls let me know if i should modify anything |
|
Fixed your dockerfile. You need to look the failing tests now |
|
I've updated the slimeweb package, no code changes. Need to re-validate to test web-socket scenario. |
|
/validate -f slimeweb |
|
just add a comment to code to force a new validation |
|
Finally passed 🎊 😭 |
|
/benchmark -f slimeweb |
|
👋 |
|
🚀 Benchmark run triggered for |
Benchmark ResultsFramework:
Full log |
|
Hmm 🤔 , I was expecting slightly higher numbers compared to my micro-benchmark. I guess it’s becoming unstable under high load. Anyway, Thanks for providing this platform for testing and support, appreciate it ✌️ . |
|
what happened to websockets, did the server died? |
slimeweb / echo-ws / 4096c (tool=gcannon) [info] waiting for server... |
It is not fully using the CPU, only 12 out of the 64 CPUs in many tests, probably some config or bad scaling |
|
Yea, Ill trigger a run with logs |
|
/benchmark -f slimeweb --save |
|
👋 |
|
🚀 Benchmark run triggered for |
Ty. That would help |
Benchmark ResultsFramework:
Full log |
|
see logs here Nº of workers seems correct but framework may have issues with high CPU count scaling, seen many like this here that eventually improved and achieved much better results |
|
Anyway, don't worry too much about results now, there is room to grow |
Yea need to check what's happening in high load and websocket. Ty |
|
Sry one last question, how do you guys check if the server is up or not for websocket scenario coz all 3 websocket test case the server is not available it showing in the benchmark log. It would be helpful for debugging. Thanks. |

Hi, I’m testing my new Python framework, could someone please take a look and confirm if everything is good?
Framework details:
Pypi: https://pypi.org/project/SlimeWeb/
Ty.