Am 03/20/2012 08:07 PM, schrieb Dave Fisher:
On Mar 20, 2012, at 11:33 AM, Joe Schaefer wrote:
________________________________
From: Mark Ramm<[email protected]>
To: [email protected]; Joe Schaefer<[email protected]>
Cc: Ross Gardler<[email protected]>
Sent: Tuesday, March 20, 2012 2:25 PM
Subject: Re: Sourceforge and AOO 3.4 distribution
On Mon, Mar 19, 2012 at 4:04 PM, Joe Schaefer<[email protected]> wrote:
FWIW the ballpark figures we have today Roberto
are roughly 12GB worth of release artifacts and
about100TB / day worth of download traffic.
Thanks for the information.
I'm working with Roberto to make sure all the right technical
resources are aligned behind him, and that we have the resources to
provide a great experience to your users. So, I'm here to help out,
and validate everything to make sure we are prepared to handle AOO's
peak load.
Based on the file size data in the previous e-mail, and this bandwidth
information, I believe we are talking about something around 700k
download per day.
Is that peak load, or is that sustained load? If it's sustained, do
you have any ideas about what peak load would look like? If not, do
you have any ideas about what sustained load would look like?
Up until the Update service broke last week, ooo was sustaining 300K
downloads a day. We used a ballpark download figure of 300 MB per user,
which may explain the discrepancy if you used something considerably less.
We simply don't have any data at this point about peak load to make
any educated guesses.
When this subject came up last year Marcus described peak as 300,000 downloads
/ day.
Yes, 300k / day was the number we have counted with. But the good news
is, it's not the peak number but average.
For new releases I don't remember any peak numbers. But I absolutely
would not be surprised when it comes to a few millions for the first
days of the new release. That should decrease considerable after ~1 week.
However, this was at Sun/Oracle times with known surprises. Now at
Apache it's a kind of new game. ;-)
What comes into my mind right now, I *highly recommend* to let the
update service response with a message like "You have the most recent
version" when we have officially announced the AOO 3.4 release in the
public.
This announcement alone (and the countless copies in the news portals)
will result in a high download peak. So, with an enabled update service
telling "We have new bits for you" *together* with the annoucement would
not be clever. The best is to do it 1-2 weeks after the announcement
when we see that the peaks are decrease considerable.
That's what we have done at Sun/Oracle and it was a good decision to let
the mirrors survive the first peak downloads.
Stats were collected until last February's switch to Kenai. See
http://www.openoffice.org/marketing/marketing_bouncer.html
Even when these numbers are from Feb 2010 it should be very similar for
2011.
Marcus
Depending on how we handle the announcement of AOO 3.4 - press, update service,
and ooo-announce we might be able to spread a single spike into more smaller
peaks.
HTH,
Dave
And finally: would you have any objection to us using a mix of fixed
mirrors, elastic file delivery services (like s3), and commercial CDN
service to handle spikes in download gracefully and assure that global
users get good download performance when local mirrors are overloaded
or not available?
No, we may even be willing to budget some amount for this purpose.
Cost estimates would be appreciated as our budget numbers for FY2012
need to be finalized next week.
I'm looking forward to working with all of you to make sure that users
have a reliable and fast download source for the upcoming Apache Open
Office release. Let me know if there's any questions I can answer
for you, or anything else I can do to help.
--Mark Ramm
====
This e- mail message is intended only for the named recipient(s) above. It may
contain confidential and privileged information. If you are not the intended
recipient you are hereby notified that any dissemination, distribution or
copying of this e-mail and any attachment(s) is strictly prohibited. If you
have received this e-mail in error, please immediately notify the sender by
replying to this e-mail and delete the message and any attachment(s) from your
system. Thank you.
