...for providing another RubyForge mirror via his company, PlanetArgon.
All mirror providers are listed here:
Thanks guys!
Yours,
Tom
...for providing another RubyForge mirror via his company, PlanetArgon.
All mirror providers are listed here:
Thanks guys!
Yours,
Tom
With the sudden influx of mirrors, what's the expected bandwidth these days? I might be able to offer up another mirror if it's down to not insane levels.
On Sep 26, 2005, at 7:25 AM, Tom Copeland wrote:
...for providing another RubyForge mirror via his company, PlanetArgon.
All mirror providers are listed here:
It's up to about 225 GB per month overall, so perhaps 50 GB per mirror.
But Dennis Oeklers kindly volunteered to shoulder half the load himself
on http://lauschmusik.de/ , so that cuts the bandwidth usage for the
other mirrors to perhaps 30 GB per month.
Yours,
Tom
On Tue, 2005-09-27 at 12:43 +0900, Gavin Kistner wrote:
On Sep 26, 2005, at 7:25 AM, Tom Copeland wrote:
> ...for providing another RubyForge mirror via his company,
> PlanetArgon.
> All mirror providers are listed here:With the sudden influx of mirrors, what's the expected bandwidth
these days? I might be able to offer up another mirror if it's down
to not insane levels.
whats the process for becomming a mirror?
Sam
On 9/27/05, Tom Copeland <tom@infoether.com> wrote:
On Tue, 2005-09-27 at 12:43 +0900, Gavin Kistner wrote:
> On Sep 26, 2005, at 7:25 AM, Tom Copeland wrote:
> > ...for providing another RubyForge mirror via his company,
> > PlanetArgon.
> > All mirror providers are listed here:
>
> With the sudden influx of mirrors, what's the expected bandwidth
> these days? I might be able to offer up another mirror if it's down
> to not insane levels.It's up to about 225 GB per month overall, so perhaps 50 GB per mirror.
But Dennis Oeklers kindly volunteered to shoulder half the load himself
on http://lauschmusik.de/ , so that cuts the bandwidth usage for the
other mirrors to perhaps 30 GB per month.Yours,
Tom
And, in broad strokes, what is the bandwidth committment to being a mirror?
Kirk Haines
On Tuesday 27 September 2005 10:24 am, Sam Mayes wrote:
whats the process for becomming a mirror?
Procedurally, just send me or Rich Kilmer an email and we can work out
the details. Technically, you just need to be able to rsync down about
1.1 GB of data to a host somewhere (rubyforge.yourdomain.org or
whatever) and then be able handle to handle the bandwidth load...
Yours,
Tom
On Wed, 2005-09-28 at 01:24 +0900, Sam Mayes wrote:
whats the process for becomming a mirror?
Right now it's about 30 GB per month.
Yours,
Tom
On Wed, 2005-09-28 at 01:38 +0900, Kirk Haines wrote:
On Tuesday 27 September 2005 10:24 am, Sam Mayes wrote:
> whats the process for becomming a mirror?And, in broad strokes, what is the bandwidth committment to being a mirror?
As the first mirror, I had committed to about 50Gb bandwidth out of my
available 100Gb. The 50Gb was blown in the first month (thanks, Curt!
-- it was because of Curt's RoR article) but settled down after that
with the addition of Dennis Oelkers's mirror. By time the fourth and
fifth mirrors were announced, I was at about 70Gb again (which wasn't
a problem; the machine isn't used for much else right now), so I
expect to go below 30Gb per month *for now*, as Dennis is soaking up
50% of the total bandwidth and the other four mirrors are handling the
50% that's left. I wouldn't be surprised if the next move is about 35%
Dennis, 35% Robby, and 30% the rest of us, because Robby has bandwidth
to spare for RubyForge, too.
The commitment is likely to be about 30Gb initially.
-austin
On 9/27/05, Tom Copeland <tom@infoether.com> wrote:
On Wed, 2005-09-28 at 01:24 +0900, Sam Mayes wrote:
> whats the process for becomming a mirror?
Procedurally, just send me or Rich Kilmer an email and we can work out
the details. Technically, you just need to be able to rsync down about
1.1 GB of data to a host somewhere (rubyforge.yourdomain.org or
whatever) and then be able handle to handle the bandwidth load...
--
Austin Ziegler * halostatue@gmail.com
* Alternate: austin@halostatue.ca
FYI... dare I say it... I blogged on the RubyForge mirror setup here:
http://tomcopeland.blogs.com/juniordeveloper/2005/09/sharing_the_rub.html
Yours,
Tom
On Tue, 2005-09-27 at 12:46 -0400, Tom Copeland wrote:
On Wed, 2005-09-28 at 01:38 +0900, Kirk Haines wrote:
> On Tuesday 27 September 2005 10:24 am, Sam Mayes wrote:
> > whats the process for becomming a mirror?
>
> And, in broad strokes, what is the bandwidth committment to being a mirror?Right now it's about 30 GB per month.
Tom Copeland wrote:
FYI... dare I say it... I blogged on the RubyForge mirror setup here:
http://tomcopeland.blogs.com/juniordeveloper/2005/09/sharing_the_rub.html
"Sharing the rub." Hehe. Dirty.
Devin
Did you consider using bittorrent ?
The more it's used for legitimate purposes, the harder it will be to do away
with it.
And you'll _never_ het slashdotted.
Cheers,
Han Holl
On 9/27/05, Tom Copeland <tom@infoether.com> wrote:
http://tomcopeland.blogs.com/juniordeveloper/2005/09/sharing_the_rub.html
Yours,
Tom
I didn't realize that was what he meant by hosting a mirror.
Robby
On Wed, 2005-09-28 at 12:27 +0900, Devin Mullins wrote:
Tom Copeland wrote:
>FYI... dare I say it... I blogged on the RubyForge mirror setup here:
>
>http://tomcopeland.blogs.com/juniordeveloper/2005/09/sharing_the_rub.html
>
>
"Sharing the rub." Hehe. Dirty.
--
/******************************************************
* Robby Russell, Owner.Developer.Geek
* PLANET ARGON, Open Source Solutions & Web Hosting
* Portland, Oregon | p: 503.351.4730 | f: 815.642.4068
* www.planetargon.com | www.robbyonrails.com
*******************************************************/
Well, honestly, BitTorrent requires that there be continuous interest in
the files being torrented. Unless the files are well seeded and/or
downloaded often, BitTorrent downloads will often be much slower than
simple FTP downloads with round-robin mirrors as have been set up for
RubyForge.
There is, by the way, exactly one file that would even remotely qualify
for BitTorrenting based on the popularity profile -- ruby182-15.exe.
-austin
On 9/28/05, Han Holl <han.holl@gmail.com> wrote:
Did you consider using bittorrent? The more it's used for legitimate
purposes, the harder it will be to do away with it. And you'll _never_
[get] slashdotted.
--
Austin Ziegler * halostatue@gmail.com
* Alternate: austin@halostatue.ca
Heh, you know, I saw that and almost renamed the post... but then
laziness took over...
Tom
On Wed, 2005-09-28 at 12:27 +0900, Devin Mullins wrote:
Tom Copeland wrote:
>FYI... dare I say it... I blogged on the RubyForge mirror setup here:
>
>http://tomcopeland.blogs.com/juniordeveloper/2005/09/sharing_the_rub.html
>
>
"Sharing the rub." Hehe. Dirty.
Yup, we hosted some large files on BT for a bit... but the torrents
really didn't get used much. Also, our tracker got hijacked (due to a
misconfiguration, my fault) which kind of left me with a bad taste for
the whole thing.
Yours,
Tom
On Wed, 2005-09-28 at 18:24 +0900, Han Holl wrote:
Did you consider using bittorrent ?
The more it's used for legitimate purposes, the harder it will be to do away
with it.
And you'll _never_ het slashdotted.
continuously offering these bittorent files, simple FTP download speed would
be the lower boundary.
Apparently there is more overhead in the bittorrent protocol than I thought.
Thanks,
Han Holl
On 9/28/05, Austin Ziegler <halostatue@gmail.com> wrote:
Well, honestly, BitTorrent requires that there be continuous interest in
the files being torrented. Unless the files are well seeded and/or
downloaded often, BitTorrent downloads will often be much slower than
simple FTP downloads with round-robin mirrors as have been set up for
RubyForge.Oh, I didn't know that. I my naivety I thought that if 4 servers were all
Yup, and even that one didn't get downloaded via BT much; folks still
just went to the file releases page.
Yours,
Tom
On Wed, 2005-09-28 at 20:27 +0900, Austin Ziegler wrote:
There is, by the way, exactly one file that would even remotely qualify
for BitTorrenting based on the popularity profile -- ruby182-15.exe.
[Delayed reaction due to me still catching up on reading ruby-talk after
no mail access for a while... Up to october 1 now...]
Han Holl wrote:
>
> Well, honestly, BitTorrent requires that there be continuous interest in
> the files being torrented. Unless the files are well seeded and/or
> downloaded often, BitTorrent downloads will often be much slower than
> simple FTP downloads with round-robin mirrors as have been set up for
> RubyForge.
>
> Oh, I didn't know that. I my naivety I thought that if 4 servers were all
continuously offering these bittorent files, simple FTP download speed would
be the lower boundary.
Apparently there is more overhead in the bittorrent protocol than I thought.
The problem as I understand it is that bittorrent is really best for distributing
small numbers of large files. A single tracker can coordinate things for lots of
files, but as far as actual seeding goes (the act most analagous to a system
providing an ftp download), it's unusual for more than a few files to be seeded
at a time. (The original bt client, I believe, would only allow three instances to
be open at a time.) This works well enough for, say, having downloads of linux
cd images. (Which is how I got mine the last time I tried doing anything with
it.) Not so good for something like rubyforge, where you have a very large number
of small files - you could make a torrent of the entire thing maybe, which would
be useful to almost no one...
I've thought off and on about a system that could deal with this sort thing better.
Something with the file verification systems like bittorrent (both to protect against
ordinary data corruption and malicious file modifications), that allowed passively
seeding files - if someone wants it, it's available, but if not, resources aren't
wasted on it. Also less dependence on a single central server, since running a
high-usage bt tracker seems to be very hard on a system. Throw in some
public/private key to allow validation of <whatever file replaces .torrent> files
that were acquired through an untrusted source...
Mostly there's three things that have kept me from actually trying to make this.
1. I don't know enough about ruby (particularly thread handling) to make it work.
2. I don't know enough about designing network protocols to make it work.
3. I doubt my ability to convince enough other people to use it to make it worthwhile.
-Morgan, hates seeing "seeds: 0"...
On 9/28/05, Austin Ziegler <halostatue@gmail.com> wrote:
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.11.14/128 - Release Date: 10/10/2005