-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
testing the limits #24
Comments
ill be taking this issue |
Great, I will expect to read a detailed plan before you start creating something, will help to understand your methodology |
if possible can you please tell me where should i start with so that i can start to learn and work on this |
@kyzolia you can start by using apache benchmark to test the api calls and their performance, and then look for concurrency based issue, locking issues in redis, basically what happens when 2 requests come with same parameters, i.e they clash at the same time? Think about similar cases where the server can break, try writing unit tests in go to test out capabilities of different function, discuss this with others to get more insight |
okay thanks for the help, ill now start to work on this issue |
Add me to this issue please |
@kyzolia, what's the progress? |
im learning more about it harshit will be helping me with it |
add me to this issue please |
can somebody write a bash script to benchmark the server and see what max concurrent load it can handle
The text was updated successfully, but these errors were encountered: