The download controller was modified on Thursday to prepare for the release of the 1.5.0.12 -> 2.0.0.4 major update. During release cycles, AMO takes abnormally high load which sometimes causes interruptions in service.
To avoid this situation we agreed to cache public download hits from the AMO install buttons. This does two things:
The benefits can be seen below. First, traffic for a web node:

Second, a CPU usage graph from the same node:

You can see the positive effect on load near noon on Wed.
The status of download counts is tracked in bug 384084. The plan is to create a background maintenance script that parses AMO logs via a cron job in off-peak hours. Counts will be updated once a day.
In addition to this, we are taking the opportunity to do a couple of things. For our summer goals, we plan on improving statistics for developers by offering:
We plan on resuming download counts early next week and update pings should be available by mid July. Thanks for your patience as we make adjustments to accomodate server load, and have a great 4th of July!
Unless I am mistaken, the effect is actually visible at 12:00 or noon rather than midnight on Wednesday.
Other than that, good article
Frédéric Wenzel on June 30th, 2007 at 11:30 pmErr, yeah you’re right — fixed that.
morgamic on June 30th, 2007 at 11:49 pm“We plan on resuming download counts early next week and update pings should be available by mid July.”
No download counts yet … Are they coming back soon? I really miss tracking my extension popularity.
Chuck Baker on July 10th, 2007 at 11:03 amAccording to AMO I had 2 downloads this week.
When will this feature be fixed?
Milos on July 11th, 2007 at 9:46 amHey,
Sorry for the delays. The download count script progress is being tracked here:
https://bugzilla.mozilla.org/show_bug.cgi?id=384084
Wil Clouser on July 11th, 2007 at 10:23 amIs the download count back to work? Why I still don’t see any update on the download count? The download of my extension is still 1:(
lwd on July 25th, 2007 at 1:22 pm