Benchmarking and scaling up #13
Comments
I'm guessing the bottleneck is on the machine where the docker daemon is running and not in glot-run itself. I can think of 3 ways to scale the docker api:
|
swarm should be the best way to go, it is an official proxy for docker daemon with extended capabilities of orchestrators. You should point more info here: |
Swarm definitely looks like the way to go 👍 |
Thanks, I'll try doing that. |
@bitsapien any success with docker swarm? I am trying to do same |
@rushi216 have not tried it. |
@bitsapien how did you set up this locally? guide me on this |
I have one instance of
glot-run
running. I did a benchmarking using 'Apache ab' with the following parameters:These are the results -
That shows a 15% success rate.
Planning to have a coding challenge for my college, and requests will be close to the above parameters. Been thinking about various approaches, one of them being where code run requests are pushed to Redis, while multiple
glot-run
nodes listen for requests, and process when available.Confused about how to go about scaling this setup. Looking for suggestions. Thanks.
The text was updated successfully, but these errors were encountered: