On 2014-12-24 05:13 (+0100), Martin Owens wrote:
In a happy Christmas time result, the issues we've been having with the very kind free CDN service from fastly.com have been ironed out and now I'm pleased to announce that inkscape.org is up and running with the new caching service effective imediatly.
So what does this mean?
(…)
Uploaded version of inkscape binaries - Because the media content is now cached, downloading the inkscape pre-compiled binaries won't incur the very high penalties if they all went directly from the webserver. So we may now be able to host all our own downloads. This is good for getting up off sourceforge.net and be able to cope with the demand.
I'm interested in suggestions on how we can stress-test the new system to make sure it will be able to cope with a new release if we decide to use it this way.
Looking at the download stats at sourceforge.net, the Windows 64bit msi installer seems to be the ideal test case: it's even larger than the OS X package (DMG), and the number of downloads by far exceeds those for the OS X build:
inkscape-0.91pre3-x64.msi ========================= 61,497 dowloads (each 96.7 MB) in December:
http://sourceforge.net/projects/inkscape/files/inkscape/0.91pre3/inkscape-0....
vs
Inkscape-0.91pre3-x11-10.7-x86_64.dmg ====================================== 1,184 downloads (each 69.6 MB) in December:
http://sourceforge.net/projects/inkscape/files/inkscape/0.91pre3/Inkscape-0....
Maybe for the last pre-release, the x64.msi package could be upload and linked to inkscape.org, while the rest of that pre-release packages is still hosted at sf.net?