Is this possible? Can this push 130 gig of transfer a month?

You could host a website on a 384/384 DSL connection, but you wouldn't be able to do 130 gigs a month, theoretical max would be about 118GB/month, and that's if the line were continually maxed out, and then you have reliability issues, a lack of peak handling ability, lack of redundancy, etc, so it's not the best idea for anything but a site where uptime and speed isn't that important.

Another question:

I have a DSL connection at 640/90. I did a wget and the transfer rate is only 60 kps. How comes its not 640 kps since my line is 640 kps.

How fast will the transfer rate be for a 384/384 line?

Your DSL connection is 640 kiloBITS per second. I'm willing to bet on your transfer you got 64 kiloBYTES per second, as that's how most software reports it. There are 8 bits to the byte.

In theory, 384 kbps. My DSL has different up and down speeds. I can get 1.5 Mbps down (close), however only 128 kbps up (which would also be the speed I could serve web pages at).

Originally posted by Travis
Your DSL connection is 640 kiloBITS per second. I'm willing to bet on your transfer you got 64 kiloBYTES per second, as that's how most software reports it. There are 8 bits to the byte.

So that means 64 kiloBYTES p s is the same as 640 kiloBITS p s?

On my dedicated rack I get 640 kps does this mean 6 megs a sec?

I'm confused? :confused: Thanks

Find out what unit your software is reporting in, to be sure. Most software reports in kilobytes per second.

There are 8 bits in a byte. So, 640 kilobits per second is 80 kilobytes per second. (Of course, you won't always hit this, depending on the speed of the site on the other end, and the links in between.)

The only time you would divide by ten is if you're talking about transfer rates across a POTS modem, where you have a start and stop bit for each 8 data bits. (Thus, it actually takes 10 bits to transmit 8 bits.)

What does RH linux shell report in?

The shell doesn't report anything - it's up to the particular command you're running. That said, most software uses kilobytes per second.

Note that between ATM and TCP/IP, the overhead is somewhere in the 5-15% range, (depends on various settings), so the direct by eight conversion doesn't quite work when it comes to real world speeds (especially when you consider that there are 1024 bytes in a kilobyte, but 1000 bits in a kilobit).

With 384/384 DSL, you'd be looking at 38-45 kilobytes/sec.

So a 1 meg line (T1) is about 100 kilobytes? right?

A T1 is actually 1.5megabits/sec, and since a T1 doesn't normally travel over ATM (as it's normally a point-to-point connection), a T1 can do approximately 170-180 kilobytes/sec at peak.

and hosting anything other than your own personal interests off of a home DSL line isn't a very good idea.

search around the boards and you'll see plenty of posts asking about hosting off of dsl...

It's alright to host a personal website or a small business website off of your DSL, although, if you wish to do several websites or sites that use up a lot of bandwidth then, it's not such a good idea.

I have 1.5mbps up and down at work and here at home. I'm quite satisfied with it, but we would never host much off of it, because you have to keep in mind that if you surf the web at the same time or download something yourself it can take away from your website, which is on the same line.

I've been hosting several websites with over 30k visitors per day combined on a 384 Kbps DSL line for two years now. The trick here is to have your pages very small and your graphics very light. Although with $99/month dedicated servers nowdays it doesn't make much sense any more.

Roughly 8 bits to the byte (I believe it's actually 8.192 or something like that), so 640/8 = 80. That would make a 640kbit line able to download at roughy 80 kilobytes per second. 384/8=48KB/sec.