Jump to content

Ubute

Members
  • Content Count

    2
  • Joined

  • Last visited

Community Reputation

5 Neutral

About Ubute

  • Rank
    Newbie

Profile Information

  • Location:
    Brisbane
  1. Exactly, capitalisation of bps (bits/second) vs Bps (Bytes/second) really makes a huge difference, and you end up trying to compare apples with oranges and leading to confusion when they're not used consistently or appropriately. Usually your network connection speed or bandwidth is expressed in bps, and file download or transfer speed data rate is expressed in Bps. Mbps (Megabits per second) refers typically to the raw throughput of the network connection, the speed of the actual 1s and 0s being transferred. Then there's transmission protocol overheads such as error correction etc which account for 10%-30% of actual bits transferred in addition to your real file data. MB/s (Megabytes per second) is typically the transfer rate of the actual data, having taken into account that overhead, and is the speed you see your file downloading at on your computer. So as a general rule of thumb, you can divide your Mbps bit rate from your speed test website by about 10 to yield the typical data transfer rate (essentially divide by 8 to go from bits to bytes, and subtract around 20% for the overheads). This explains John Heaton's real world experience of ~4 MB/s download speed with his 48 Mbps connection. He's actually used up pretty much his entire bandwidth there and the Orbx servers appear to have easily coped in that example. Let's assume the 21GB installation size gets packed and compressed down to 15GB download size (no idea on actual figure, just picked a number out of thin air). On my crusty ~8Mbps ADSL, I'd be looking at around 5.5hrs best case to download it, assuming the kids aren't hogging my bandwidth with YouTube etc and the Orbx servers are up to the task with everyone hammering them.
×
×
  • Create New...