Downloading 2023

Jim McGinnis · From: Owasso, OK USA

I just recently purchased and downloaded the online version of BIB 2023.
It took hours to complete the download.
Is it my computer/internet or has others had this problem?
_________________
Jim McGinnis

Dave Mudgett · From: Central Pennsylvania and Gallatin, Tennessee

I just downloaded the base Pro version last night. 98% of it downloaded within 20 minutes, and then it took 3 hours to finish the last 2% at near-dialup rates (circa 50-100 kbps). I should have done an ookla speedtest to see if my ISP was throttling me or running low on bandwidth (it's a 32 GB download and it was NYE) or if the issue was at the BIAB end - but there was New Years Eve stuff going on, so I didn't birddog it.

It did finally download, and they told me that the download link is good for 5 years.

Bob Shilling · From: Berkeley, CA, USA

New to BIAB. I just purchased the 2023 Pro version three days ago (12/29). It took about 45 mins to download and install. I also ordered the $15, USB backup. That came by USPS yesterday. It's simple to get started, but looks like a steep learning curve to really get into it.
_________________
Bob Shilling, Berkeley, CA--MSA S10, "Classic"

Dave Mudgett · From: Central Pennsylvania and Gallatin, Tennessee

FYI - I went in and tried to re-download one of the two files that were taking so long, which were realtracks_pro_12.exe and realtracks_pro_13.exe - I tested on realtracks_pro_13.exe. The average download speed is 60-70 KB/s = 0.6-0.7 MB/s, while the speedtest for my ISP is showing 740Mb/s or about 92MB/s for downloads. Estimated completion time for just that roughly 1.2GB file is over 3 hours. So my bottleneck is between my ISP and pgmusic. I called it quits after a few minutes, the goal was to simply see if it was still slow.

It may be a general bandwidth issue, or perhaps there is something with those two particular files. As I stated earlier, I got most of the download (about 29 GB) in about 20 minutes to start. That implies a rate of about 30,000MB/(20min*60s/minute) = 30,000MB/1200s or about 25MB/s, which is a bit more than a quarter of the potential bandwidth of my connection. And it took over 3 hours to finish the remaining GB or two. So there is a major bottleneck somewhere beyond my ISP.

Jim Fogle · From: North Carolina, Winston-Salem, USA

Dave,

You may find the utility app, WinMTR, useful.

Dave Mudgett · From: Central Pennsylvania and Gallatin, Tennessee

Jim, one doesn't need a windows gui program to do a traceroute or ping. I did that via the command line, there was nothing funny going on. Traceroute from here to pgmusic.com = 70.38.54.188 shows about 14 hops, and pinging gives a packet round-trip time of about 40 ms. Did then and still does.

So there's absolutely no connection problem, per se. The throughput on a large file was just very slow, and not between me and my own ISP. I did try some downloads elsewhere, and they were speedy as could be, even as the pgmusic download was slagging at sub-100KB/s speeds. I got my download, and that's all that really matters. They were doing a hard push with end-of-year specials, so it may have just been heavy traffic on their server. And as I stated earlier - most of the files downloaded at a very fast rate before it started to slag.

FWIW, the traceroute to the forum was/is much more dicey, and pinging gave (and still gives) a packet round-trip time of around 82 ms. Pretty typical for coast-to-coast, where even speed-of-light propagation delay of at least 4000 km at roughly 1ms/100km gives a roughly 40 ms latency floor. I gather the closest pgmusic server is in Montreal, which explains the lower, roughly 40 ms, round-trip packet latency to pgmusic.

Forum Index > Band-in-a-Box		Next oldest topic :: Next newest topic

All times are GMT - 8 Hours	Jump to: