9
Ataboy, on 02 October 2013 - 08:45 AM, said:
I have Avast but do NOT have an AMD processor. My processor/chipset is intel. The last 2 patches (17th and Oct 1) the DL speed has been excruciatingly SLOW. I mean slow to the point that it would take days to complete if I left it running. My inet DL is 6Meg. Speedtest shows all is good. Tracert shows no problem getting to patcher.mwomercs.com. All pings in tracert between 10 and 30ms. So today(wed oct 2nd) I decided to uninstall and reinstall. Started this at 7am eastern. The 1st 2gig came down as expected less than 1 hour and then it slowed to a vitual halt. So I did tests again ----> Speedtest shows all is good. Tracert shows no problem getting to patcher.mwomercs.com. All pings in tracert between 10 and 30ms. All appears that the patcher server is slowing down to an almost standstill with my patcher. I have: 1. Uninstalled reinstalled avast and rebooted - rerun patcher - same problem it has been 40 minutes now and I am at stuck at 2.35MB / 2956MB with the PLEASE WAIT. 2. I have unchecked "Enable hardware-assisted virtualization" and rebooted -- same problem 3. Following a suggestion from Avast I have excluded the Piranha Games folder and all sub folder 4. I have tried using the repair tool to get the files down. Rebooted after each and none of these have provided any change. This issue has been outstanding for some time. Could someone from PGI please post in this thread whether or not it is actively being worked on so those of us that are effected can stop wasting our time. Thank you
Well, this is kinda unrelated to the original intent of this thread, but, sure, I'll respond. First of all, I highly doubt it has anything to do with Avast. It's certainly not related to the problem with the game discussed in this thread. This is almost certainly a toss-up between peak times (ie. many other users downloading at the same time) and slow/unpopulated nodes. Very roughly, the way the CDN works is to distribute the files being downloaded to nodes that are closer to you (the person downloading the given file). If you are the first person to download via that node, then the node itself has to receive the file from either the origin or the next nearest node. If, on the other hand, the node already has this file then you're in luck and the transfer will go through much more quickly.
So, what's most likely is that you tried getting the patch when two conditions were met: first, the node didn't have the patch file; second, the origin (or next nearest node) were under a heavy load, slowing down the transfer to your local node.
As to whether or not this is actively being worked on, well, to a certain extent it's out of our hands. We're constantly working on ways to improve the overall experience and efficiency of the patching process. Unfortunately there's nothing we can really do to speed up the CDN, so we have to focus on our utilization of the CDN. But the truth is simply that new patches will take time to spread across the nodes. You're more likely to get a good speed later in the day on patch days than immediately after the patch is released. But someone will have to take the hit with a slow download as the node is being populated. It's just the way a CDN works. Like I said, this is out of our hands - it's the way the technology works.
If you would like to continue discussing this, please either start a new thread or just PM me. This thread is specifically to discuss the Avast/AMD "Please Wait" crash issue, which you don't seem to be having. I'm not opposed to discussing this issue (as time allows), but let's do it in the proper channels.
Thanks,
Krist
