> The feature was so great that we started to overload the npmjs.org service.
I'm not sure I would call my feature "great" if it could have brought down npm.
Visual Studio Code 1.7 overloaded npmjs.org, release reverted
11–20 of 94 posts
Re: Visual Studio Code 1.7 overloaded npmjs.org, release reverted
#12Damn it, M$! Keep your shit closed. Not everybody wants you messing around.
[deleted]
Re: Visual Studio Code 1.7 overloaded npmjs.org, release reverted
#13I'd just like to say on behalf of npm that Microsoft's handling of this incident was A+. As soon as we alerted them to the issue they were all hands on deck and did a rollback.
We've been really pleased that Microsoft chose to put their @types packages into the npm registry rather than a separate, closed system, and in general happy with Microsoft's support of node and npm. We're confident we can make the new features of VSCode work, we just need to work with Microsoft to tweak the implementation a little.
This was an honest mistake on their part, and we caught it in time that there was very little impact visible to any npm users.
Fun fact: at its peak, VSCode users around the world were sending roughly as many requests to the registry as the entire nation of India.
Re: Visual Studio Code 1.7 overloaded npmjs.org, release reverted
#14I'd just like to say on behalf of npm that Microsoft's handling of this incident was A+. As soon as we alerted them to the issue they were all hands on deck and did a rollback. We've been really pleased that Microsoft chose to put their @types packages into the npm registry rather than a separate, closed system, and in general happy with Microsoft's support of node and npm. We're confident we can make the new feature…
Can you elaborate on what the issue is and how you want it to be fixed? Is it just something like rate-limiting requests or something more fundamental?
Edit: Answered at https://news.ycombinator.com/item?id=12861118
Re: Visual Studio Code 1.7 overloaded npmjs.org, release reverted
#15> The feature was so great that we started to overload the npmjs.org service. I'm not sure I would call my feature "great" if it could have brought down npm.
I thought that sentence sounded very trump-ish.
The feature was so great that npmjs couldn't keep up with it, it was yuuuuuge!
Re: Visual Studio Code 1.7 overloaded npmjs.org, release reverted
#16Shouldn't all these requests be cached by a CDN? What exactly is overloading?
CDNs don't usually cache 404s. VSCode was looking for @types packages for any and every npm package its users were using. Packages that had a type description caused no issue, but most packages don't, so we had a > 1000% spike in 404s. Our workaround before MS did the rollback was to cache 404s for @types packages specifically, and it was effective enough that the registry never really went down.
Re: Visual Studio Code 1.7 overloaded npmjs.org, release reverted
#17If I were on the Azure team I'd be offering tons of free credit to npmjs.org to get them to use Azure. Azure coming to the rescue would be the perfect ending to this story for Microsoft.
CDN caching globally, please!
Re: Visual Studio Code 1.7 overloaded npmjs.org, release reverted
#18I'd just like to say on behalf of npm that Microsoft's handling of this incident was A+. As soon as we alerted them to the issue they were all hands on deck and did a rollback. We've been really pleased that Microsoft chose to put their @types packages into the npm registry rather than a separate, closed system, and in general happy with Microsoft's support of node and npm. We're confident we can make the new feature…
So one day they switched their entire user base to rely on a 3rd party free service without any load testing or heads up? What could possibly go wrong?
Re: Visual Studio Code 1.7 overloaded npmjs.org, release reverted
#19Shouldn't all these requests be cached by a CDN? What exactly is overloading?
CDNs don't usually cache 404s. VSCode was looking for @types packages for any and every npm package its users were using. Packages that had a type description caused no issue, but most packages don't, so we had a > 1000% spike in 404s. Our workaround before MS did the rollback was to cache 404s for @types packages specifically, and it was effective enough that the registry never really went down.
Interesting. Thanks for sharing this information.
Re: Visual Studio Code 1.7 overloaded npmjs.org, release reverted
#20Damn it, M$! Keep your shit closed. Not everybody wants you messing around.
We've asked you twice before not to do this, so we have to ban this account. We're happy to unban accounts if you email us at hn@ycombinator.com and we believe you'll not do this in the future.