Stress Test Before Deployment

[nleroy917]

I need to stress test all routes of the API before deployment to find huge issues or bottlenecks.

Will definitely use the following python package to do so: https://github.com/locustio/locust

[nleroy917]

Used locust to stress test. Some summary data:

• Main route / : 1000's of requests per second
• Get tracks /playlists/{playlist_id}/tracks : 10's of requests per second
• Get analysis /{playlist_id}/analysis : 1-2 requests per second

Need to update performance of analysis route - I am hitting the Spotify API rate limit. See issue #18 for details and tracking. Will update when another stress test is done.

[nleroy917]

API underwent serious refactoring to conduct analysis... new stress test results:

• Main Route / : Test passed at a steady rate of 15 requests/second
• Get Tracks /playlists/{playlist_id}/tracks : Test passed at a steady rate of 8 requests/second (one rate limit error was hit)
• Get analysis /{playlist_id}/analysis : Test (sorta) passed at a steady rate of 5 requests/second (some rate limit errors were hit).

It seems that in terms of scalability and performance - Spotify's rate limits designated to my application will be the ultimate bottleneck. I think we should be good for now to deploy and promote and that even a steady stream of users wont break the application.

Only once serious traffic is being achieved will I need to consider a Spotify partnership or seriously refactoring the API.

Closing the issue for now.