Skip to content
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

Support GPMDP #56

Open
zeke opened this issue Jun 7, 2018 · 3 comments
Open

Support GPMDP #56

zeke opened this issue Jun 7, 2018 · 3 comments

Comments

@zeke
Copy link
Contributor

zeke commented Jun 7, 2018

@MarshallOfSound would like to use this service for https://electronjs.org/apps/google-play-music-desktop-player but is concerned about the request volume, as the app is very popular.

@MarshallOfSound can you share your usage numbers, or what you think would be a baseline for load testing?

@juliangruber I recall you doing some load tests on this service, right?

Let's see if we can make it work.

@juliangruber
Copy link
Contributor

I have done some basic load testing using my machine until the internet gave out, and that was fine, but no, not yet used one of those services to generate some real load.

I'll set something up once @MarshallOfSound gives us some numbers :)

@juliangruber
Copy link
Contributor

Also, maybe you can share your current update service deployment?

@MarshallOfSound
Copy link
Member

MarshallOfSound commented Jun 11, 2018

@juliangruber Currently we get (according to cloudflare) around 120,000,000 requests a month which translates to approximately 4,000,000 a day and approximately 45 a second. Around 70% of those are handled by cloudflare, the rest hit a single vertically scaled server running a modified version of nuts to have better (read more aggressive) caching. That server currently averages 60% load and spikes to 80% during PST. I use pm2 to cluster that nuts instance 12 times.

That servers specs are currently an E5 1650 v3 and way too much RAM (like 96GB).

Please note this may just be that nuts is not very optimized (I had to put a lot of custom caching in).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants