On 5/30/13 9:04 AM, Russel Winder wrote:
> It seems that download speed is about 500b/s, so about 3 weeks to
> download :-(
>

Hrm.. what happened to the links on the download.html page?  They should all be pointing at an s3 url:

    http://downloads.dlang.org.s3-website-us-east-1.amazonaws.com/releases/2013/

Yes, the sort order on that page is wanting.  But it's not intended to be _the_ download page, just a quick way to see the underlying files if needed.

Andrei/Walter, why happened?

On Thursday, 30 May 2013 at 16:48:38 UTC, Brad Roberts wrote:
> On 5/30/13 9:04 AM, Russel Winder wrote:
>> It seems that download speed is about 500b/s, so about 3 weeks to
>> download :-(
>>
>
> Hrm.. what happened to the links on the download.html page?  They should all be pointing at an s3 url:
>
>     http://downloads.dlang.org.s3-website-us-east-1.amazonaws.com/releases/2013/
>
> Yes, the sort order on that page is wanting.  But it's not intended to be _the_ download page, just a quick way to see the underlying files if needed.
>
> Andrei/Walter, why happened?

Any idea if these match what was uploaded to dlang.org?  I know there was a do-over on the final release.

On Thursday, 30 May 2013 at 16:53:24 UTC, Brad Anderson wrote:
> On Thursday, 30 May 2013 at 16:48:38 UTC, Brad Roberts wrote:
>> On 5/30/13 9:04 AM, Russel Winder wrote:
>>> It seems that download speed is about 500b/s, so about 3 weeks to
>>> download :-(
>>>
>>
>> Hrm.. what happened to the links on the download.html page?  They should all be pointing at an s3 url:
>>
>>    http://downloads.dlang.org.s3-website-us-east-1.amazonaws.com/releases/2013/
>>
>> Yes, the sort order on that page is wanting.  But it's not intended to be _the_ download page, just a quick way to see the underlying files if needed.
>>
>> Andrei/Walter, why happened?
>
> Any idea if these match what was uploaded to dlang.org?  I know there was a do-over on the final release.

Nevermind.  My dlang.org download finally finished and the two appear to be identical.

On Thu, 30 May 2013 12:48:27 -0400, Brad Roberts <braddr@puremagic.com> wrote:

> Hrm.. what happened to the links on the download.html page?  They should all be pointing at an s3 url:
>
>      http://downloads.dlang.org.s3-website-us-east-1.amazonaws.com/releases/2013/

Oh, that's MUCH better.  Couple seconds instead of an hour.

-Steve

On 5/30/13 9:53 AM, Brad Anderson wrote:
> On Thursday, 30 May 2013 at 16:48:38 UTC, Brad Roberts wrote:
>> On 5/30/13 9:04 AM, Russel Winder wrote:
>>> It seems that download speed is about 500b/s, so about 3 weeks to
>>> download :-(
>>>
>>
>> Hrm.. what happened to the links on the download.html page? They should all be pointing at an s3 url:
>>
>> http://downloads.dlang.org.s3-website-us-east-1.amazonaws.com/releases/2013/
>>
>> Yes, the sort order on that page is wanting.  But it's not intended to be _the_ download page,
>> just a quick way to see the underlying files if needed.
>>
>> Andrei/Walter, why happened?
>
> Any idea if these match what was uploaded to dlang.org?  I know there was a do-over on the final
> release.

Unless there was yet another re-spin after the 3rd or 4th or whatever one it was late last night, then yes, they are.  Here's the md5 hashes for what's on s3 right now:

eae22a07b7a460c82d0e7aeccf3ce0b4  dmd_2.063-0_amd64.deb
84a5d39125903065b07227256915ebf6  dmd-2.063-0.fedora.i386.rpm
2da09890852824b60a8bc00a89d952a5  dmd-2.063-0.fedora.x86_64.rpm
dafc9eb2e8fc602fd4371a0b246702fb  dmd_2.063-0_i386.deb
eb152c2e8f6ff5a4967557c462466aba  dmd-2.063-0-i386.pkg.tar.xz
ed401223a4fb09fdf76c17b8b2166903  dmd-2.063-0.openSUSE.i386.rpm
83ba0226b5c72f3df5acce3a9108f433  dmd-2.063-0.openSUSE.x86_64.rpm
b6dffab3edae5c258423b7d4411d31d2  dmd-2.063-0-x86_64.pkg.tar.xz
19f560665c242b2034eeaff9094b8e11  dmd-2.063.exe
93cfbcece3cf4eca37b6582f91722c7d  dmd.2.063.zip

On 5/30/13 12:48 PM, Brad Roberts wrote:
> On 5/30/13 9:04 AM, Russel Winder wrote:
>> It seems that download speed is about 500b/s, so about 3 weeks to
>> download :-(
>>
>
> Hrm.. what happened to the links on the download.html page? They should
> all be pointing at an s3 url:
>
> http://downloads.dlang.org.s3-website-us-east-1.amazonaws.com/releases/2013/
>
>
> Yes, the sort order on that page is wanting. But it's not intended to be
> _the_ download page, just a quick way to see the underlying files if
> needed.
>
> Andrei/Walter, why happened?

I am the one who switched to download over HTTP. The reason is that I hadn't anticipated the enormous demand following the announcement, and we really need to collect download statistics, which are already built in dlang.org. You mentioned those can be gotten from S3, so I'm counting on that.


Thanks,

Andrei

On Thu, 30 May 2013 16:13:13 -0400
Andrei Alexandrescu <SeeWebsiteForEmail@erdani.org> wrote:
> 
> I am the one who switched to download over HTTP. The reason is that I hadn't anticipated the enormous demand following the announcement, and we really need to collect download statistics, which are already built in dlang.org. You mentioned those can be gotten from S3, so I'm counting on that.
> 

I don't know what sort of software is running dlang.org, but it should be easy to toss together a trivial "http://dlang.org/trackLink/targetURL" url. If you're using a log-analyzing stat package like webalyzer, then all you should need to do is make "http://dlang.org/trackLink/targetURL" redirect to "targetURL" and do literally nothing else.

You may not even need a script at all for that. As long as the pre-redirect URL gets logged (I don't recall if they usually are or not - but I *think* so), then all you'd have to do is toss a trivial rewrite rule into Apache's/Nginx's/whatever's config file.

On Thursday, 30 May 2013 at 20:13:14 UTC, Andrei Alexandrescu wrote:
> I am the one who switched to download over HTTP. The reason is that I hadn't anticipated the enormous demand following the announcement, and we really need to collect download statistics, which are already built in dlang.org. You mentioned those can be gotten from S3, so I'm counting on that.

You need to explicitly configure access logging for S3 buckets though (logs are stored in a second S3 bucket).

David

On 5/31/13 8:52 AM, David Nadlinger wrote:
> On Thursday, 30 May 2013 at 20:13:14 UTC, Andrei Alexandrescu wrote:
>> I am the one who switched to download over HTTP. The reason is that I hadn't anticipated the
>> enormous demand following the announcement, and we really need to collect download statistics,
>> which are already built in dlang.org. You mentioned those can be gotten from S3, so I'm counting
>> on that.
>
> You need to explicitly configure access logging for S3 buckets though (logs are stored in a second
> S3 bucket).
>
> David

Relax.. it's all covered.  The logging has been enabled since the s3 bucket was created almost a year ago.  We've been using s3 for a long time now and NOT using it with this most recent release was a fumble.  The whole release day should have been a non-issue from a bandwidth part.