Patch servers Running very slow for the last year

I’ve noticed the following over the last year or so and decided to make a video to back it up (show us the proof or it didn’t happen).

Started a HS update today and can provide the following feed back on your patch servers.

  1. Initialization process took 4 minutes 21.5 seconds (actual was 4:21 and 29/60 fps

  2. It reports it is installing files during the initialization, yet nothing has been downloaded, there is no down bandwidth utilized, and no activity on installation drive. How can it be installing files if hasn’t d/l any yet, and it’s not using any access on the installation drive?

  3. Ran a speed test during initialization, as well during actual d/l and install and maintained an average of over 800Mbps (100MBps) inbound. The BEST your patch servers where able to achieve was 2.5MBS (20.48Mbs) .

  4. I can run netflix or any other streaming service at the same time as playing, with no hiccup to either. It only seems to impact the patch server. Doesn’t matter what app of yours is being updated through your client, results are the same, with or with out other stuff running. If there is other stuff running, they are lag free, while your updater appears no different whether it’s stand-alone or not.

can be found at: youtu.be

/35bAkKxr0X0

I’d apologize for the vid being over 7 mins long, but that’s dependent upon Blizzard, the Bnet app, and the speed of their initialization process, and not my mistake or misjudgment during post. If I cut stuff out or sped it up, I’d be called out on making a fake I’m sure.

So what’s the issue here? Certainly not my internet. Perhaps you guys should try reinstalling and deleting temp files? Seems like the standard go to for speed issues. Don’t ask me where I got that novel advice either.

Trust me, it’s supposedly from a very knowledgeable, no corner cutting source. I’m confident you can trust them if you follow their suggested steps for speed issues.

edit: of course it could be brought up that initialization has nothing to do with internet speed. It’s either happening on my system, their systems, or a combination. If my system is involved in an initialization process for download patch files via udp (or even TCP for that matter) I can’t imagine on my part what would take an 8 core 16 cpu processor over 4 minutes to arrange and orchestrate the start of downloading.

Now if their systems are involved, it’s either their connection, their systems as clearly my 152ms return (there and back) can’t be the issue. if it was, the manifest, ip, port establishments information to start a d/l would exceed the size of the actual d/l given that it took less time to d/l the patch than it did to initialize. Not highly likely imo.

This issue comes up in waves each year. I’m not sure what the cause is, as I’ve never been able to replicate it. Due to the recent posts, I decided to test a few game downloads for titles I’m not currently playing.

Here’s my D4 install from last week. The connection never dipped below 100 MB/s.

Imgur

Yes, it is possible other factors cause this, such as a slow/old drive, security software, or connection throttling. It’s tough to pin down the cause as it might be different across the group of people experiencing it. For instance, one report was maxing out the available download bandwidth without disconnecting the rest of their internet connection. Here’s that case.

Note: I am a volunteer.

I’m not too worried about the D/L speed of the actual patch. I know that can fluctuate for various reason, but when it spends 4+ mins initializing… What the heck is it trying to initialize for 4 mins, a nuclear launch?

As I said, and the video shows…it took longer (25% roughly) to initialize, than it did to download the entire last patch.

Reorganizing pak files to make the download more efficient. If the drive is slow or too full (or another drive is very slow), the process takes longer.

That would stand to reason IF something such as pak files had been downloaded or are you referring to Blizzards drives on their patch servers?

Also it’s safe to assume, that the majority of players trying to get the same patch, have the same game version being updated. If there was an optimal order of pak files, it should be the same for each, and once it is organized once, it should remain the same in those cases and shouldn’t need to be reorganized each time.

Sure If I was trying to patch the game from a version that hadn’t been patched in a year or two, I could see the reorganization delay and need.

If we micro analyze the process it becomes more obscene.

  1. launch battlenet
  2. authenticates in 1 min max
  3. determines all versions of all games installed, and prompts which ones need updating in under a minute.
  4. I click update.
  5. It sits for 4 mins doing nothing other than reporting it’s initializing.
  6. it d/l’s, installs, and removes temp files in 3 minutes. Bandwidth increase to > 0 as does install disc location utilization. and I can click play

What is actually going on during step 5

This is before the download starts and it says initializing for 4 mins, then proceeds to download and install (including the reorganization) in 3 mins, making the total process 7 mins long.

During the 4 minute initialization wait, there is no disc activity, nor any bandwidth utilization. So what is it doing for that 4 mins. I would assume something on their side to setup and start the actual d/l.

Like is there a manual D/L and install method I could use. if the d/l and install completion only took 3 mins. I’m sure I could navigate to and initiate the download sooner than than 4 mins.

There isn’t another way to update that I’m aware of. That said, I guess I don’t find the wait time as that big of an inconvenience or take notice of step 5, at all. Initialization usually takes 30–60seconds on my PC.

Yeah it’s not a pc issue as you are trying to insinuate.

3.8Ghx {boost 4.2Ghz} proc Ryzen 7 (8 core, 16 cpu’s)
32G Ram
Install drive: 4TB drive (g: - drive 4 of 7, 5 of 8 if you include cd/dvd/blueray burner)
Vid: RTX 4080 Super.

Inet: 125MBs down / 30 MBs Up ( or in bits: 1000Mbs down 240Mbs up) but inet speed is irrelevant to initialization as it takes place either on the sender/or receiver’s system before any inet is utilized and dependent upon transfer speeds.

Given the above stats, if my system was the sole responsibility for initializing a d/l. what could possibly be taking it 4 mins to initialize, yet only take 75% of the time to follow through on it’s determination? Remember though there is 0% disc usage, so nothing is being read/written on my system during the 4 minutes, and there is 0% inet usage, so there is nothing being transfferred. That 4 mins or 240’s would be 100% processing, or about equal to (low) 228,000,000,000 bits or 28.5 GB processed by my processor at full capacity of that time. Since I’ve already established (or can through another video next patch) that even though my processor is capable of doing other things like OS, background services, streaming, video decoding, the impact and capability to my system is negligible to the overall system resources available to spend 4 mins do some sort of calculation over 4 mins to be able to initiate a d/l of files via manifest, it seems very clear that the 4 minute delay is a result of their systems not being able to start it for 4 minutes (who knows… maybe it’s a hidden timer or queue system. Maybe it’s inferior drives and processors as you suggested on their end. Maybe it’s selective targeting of preferred customers. But what ever it is, it is not my system, nor my inet connection (which is clearly irrelevant).

I mentioned other reasons initializing can take longer, but made no claims about your system specifically, only my own. I am not able to replicate long wait times while initializing to apply patches or install games.

This forum is for players to assist other players with crash or install issues of the Bnet client itself. Since you’re asking about the design of Blizzard’s software when updating games, which is outside the scope of this forum, there isn’t anything else I can address for you.

Ok I get it.

Some customers experience longer than expected initialization times while others do not.

It is not a technical issue, and not worthy of ascertaining why, and making it so that all customers experience relatively similar initialization times.

My reply has no hidden meaning about what is or isn’t worth Blizzard’s time. I also stated that I am a volunteer in my first reply. Volunteers do not have customers, nor do we tell Blizzard how to use their resources.

Of course, and neither was I implying there was a hidden meaning. Only the meaning that was written and those things that are generally accepted as fact.

Perhaps I am mistaken, but this appears to mean that this is a a Blizzard owned, operated, and controlled forum. It also appears to mean that though there are many things that could be considered a technical problem, only those problems whom fall in the categories of crashes or installs are eligible for support, and all other technical issues and problems that don’t fall into those two categories are not eligible for support of a technical nature.

The reason why (i’m assuming here) you detected (as some might say) a tone to my response is the following.

I was under the impression that all technical issues and problems that a customer of the forum owner/operator experience with the bnet client, could or should expect support for their technical issue in the technical support forum. I don’t think it’s an unrealistic understanding or expectation.

When you said:

I feel it reasonable that in order to determine concretely if there is some sort of technical problem with the initialization process, (thereby (imo) the technical problem could be expected to receive support from the technical support forum) One needs to know or understand how it is supposed to operate so they can compare that to how it is actually operating, and thereby be able to determine if there is a problem or not. If No one knows how it is supposed to operate, how are they going to know when it’s not working as intended and when it is?

So yes, I wanted to know how it’s supposed to operate, what it was supposed to be actually doing and compare that to my experience. Who knows, maybe that’s how it is supposed to operate? But as you said, you don’t know, and no player can be expected to know, so therefore no one other than Blizzard has any idea if it’s normal or abnormal operation. Leaving it up to players to determine if it’s a problem or not, when they have no idea how it’s actually supposed to work seems a bit fruitless simply by concept of process. I’m sorry that you did not see the relevance of the inquiry as related to a potential technical problem that I thought could be supported in a technical support forum.

Edit:

I felt I should speak to the deeper meaning of the terms customer vs. player. Yes we are all players but that does not exclude us from being customers. The term customer does impart an understanding of more responsibility or onus on the seller to address problems with their facility, product, or in this case an app for customers rather than just players who are not customers.

Take a company for instance that owns a tennis court. If you go in and play, but did not pay to use the court, you are a player, but not a customer. If you find that the net is sagging, the lines are fading and wearing, sure you can bring it to the attention of the owner operator (or complain as some people may say) but since you have not paid to use it, there is less of an expectation on the owner operator to address the issues raised. Conversely, if you pay to use the court each time, not only are you a player, but you are also a customer. This in and of itself through linguistics as influenced by this societal culture, generally sets and has an understanding that there is more reasonability by the owner operator to address issues raised. Mainly because if not, the customer may cease to be one.

This is one of the nuances that is used by Blizzard (and a lot of other companies). Referring to participants as players, to subconsciously set in peoples minds a lower responsibility on their part, rather than customers which would setup a greater expectation from them.

Edit 2:

13 hours since I posted this, and suddenly… mvp forum patrions are silent, They obviously can’t handled learned responses. Not that I expected anything less. they are quick to respond when they intially believe the poster is 12 and under and have an intellectual capability par to that. But when they are confronted with a customer who responds that has greater than a year 2 University education… they fall silent until they are called out on it and scramble to come up with some retort to save face. Would any one care to provide a word that does not violate forum rules that describes that? I bet all the employee’s of Blizzard would be unable to accomplish that.

Oh look, I called them out, made them look bad, so we might as well deleted the topic, ban the user, before we look bad to the learned folks in the world…

Edit 3:

I shared edit 2 with someone who has never played a Blizzard game. If they actually remember the name Blizzard, guess what’s going to be the first thing that comes to mind? And don’t get me wrong, as we work on replacing a fence in the next week or two, I’ll be elaborating on context, and additionally all the issues I’ve experienced, especially including all the ones that my topics have been deleted, and bans implemented because it paints Blizzard in a less than favorable light, by stretching the meaning of words of their TOS/EULA to encompass outliers in meaning as if they are the predominate meaning.

Man if someone who actually knew anything about this technical issue responded, asked questions, and provided advice, I wouldn’t have as much time to analyze and comprise edits like this.

Of course we all know that Blizzard moderators are unable to edit and remove offending parts of a post, and can only remove posts in their entirety (which is a load of poppy-c$%k, that’s a popcorn from the 1920’s not profanity but your automated or ai parser is not advanced enough to recognize that) rather than edit and remove ONLY the offending portions, but that would be contrary to their agenda of preventing educated and learned customers from educating other players about their shortcomings and areas that they need to improve upon.

Moderator Edit: Yes, we actually can edit to remove specific text from a post. We often do not, as part of the penalty of violating the Code of Conduct often is having the entire post deleted.

BTW: Poppycock is believed to be derived from the Dutch word pappekak, earliest use in American English around 1865. Though root of the word is disputed amongst entomologists.

Also: According to Lincoln Snacks, Poppycock was invented by Howard Vair in the 1950s as a snack to accompany him on road trips. In 1960, Wander, a Swiss company, bought the rights to Poppycock and moved production to their Villa Park, Illinois, facility.

I agree with Duke, the initialising and the download speed is very slow almost all of the time. The battle net app is terrible imo.

Again, you are not my customer. I do not profit on your Bnet purchases or whether you choose to play games hosted on Bnet. I am a volunteer and do not work for Blizzard. I provided this information already, please make note of it. Responding only gave you license to continue waxing poetic about the situation.

Additionally, it’s impolite to judge someone’s intelligence based on the plain language they use in a forum. How would you feel if someone pointed out all of the grammar mistakes you made in this thread? This is a rhetorical question.

This statement is completely false. They can remove parts of or all of any post in any of their Bnet or game forums.


Edit 1:

I want to spend time answering others so I must move on from a discussion that has gone sour due to lack of understanding what information is and is not available.

Good luck resolving your issue.


Edit 2 & 3:

Removing since the thread is mercifully locked.