Reserved bandwidth??
this post was submitted on 07 Mar 2024
13 points (100.0% liked)
linuxmemes
24512 readers
1914 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
It's used for updates. I'm not sure if it works all the time.
I think that it used to be called superfetch in the old days. https://answers.microsoft.com/en-us/windows/forum/all/superfetch-service-disable-helps-to-increase-speed/3c4d5b4b-edef-4eb7-9456-52fd304e606c
If you're using an "unofficial" license, it's probably normal to disable updates and afferent services.
I remember from years ago when I was modding Windows XP installations with nLite to try to purge all the unnecessary bits and install some useful stuff. Superfetch was this annoying service that supposedly ruined online gaming due to lag. :)
Prefetch and superfecth are just obnoxious services that waste disk space. You can safely disable them, there is no downside to not using prefetch or superfect on modern SSDs. On regular spinning drives, yes, they did make loading programs a bit faster.
Some sort of hidden, concealed, clandestine internal QoS implementation in Windows. Reserving a portion of network bandwidth for high priority traffic sounds like a good concept, but I don't like the fact that this is so hidden (I've been working with computers for many years and I've never heard of it until now), and that the mechanism to determine the priority of a packet is unknown.
We know windows spyware traffic have the top priority.
https://www.makeuseof.com/windows-limit-reservable-bandwidth/
It's not as scary as it sounds.
It's not, and in a vacuum I don't think anyone would mind. It is the fact that it is concealed that is really shitty.
"It reserves bandwidth for high-priority tasks such as Windows Update over other tasks that compete for internet bandwidth, like streaming a movie"
As much as I'd like to keep my system up to date (and I really do), if I'm watching a movie then that is my priority. Any task I'm currently using the bandwidth on, should be considered my system's priority. This is akin to rebooting the computer when it determines it is necessary, with the user having little control to stop it; it's intend isn't malicious, and it is meant to protect the user, but all it achieves is upsetting the user and make us find ways around it or turn it off completely.
I mean that only matters for people like us.
99.99% of the Windows user base doesn't give the tiniest semblance of a shit about any of that. Hell I run Windows on my gaming pc still and have never had cause to do any of that.
| what if you | wanted to show a presentation |
|---|---|
| but windows said |  |
I'm going to be honest with you, as often as this has been memed and for as long as I have been using Windows on my work computer, I have never once been forced to restart on the spot by an automatic update.
I'm sure those who have will be quick to reply but at this point I'm 90% confident it's a loud minority.
Yes, because even once is too many.
In a corporate, I spent an hour and half every morning waiting for Windows to update. Then my coworker handed me Fedora DVD and I never looked back.
I'm saying it's never happened to me. Not once. Zero times. Zero is less than one.
Normal Windows updates don't take an hour long. Give me a break. The ones that do are the version upgrades. That's like the equivalent of a distro upgrade.
Normal Windows updates don't take an hour
Correct. But who can tell the difference beforehand between a normal update and an abnormal one? The problem is Windows tends to hide those details. I've sat on support calls where a server needs to be rebooted for some configuration change, and Windows insists on applying updates because hey, you're rebooting anyway, so what if it takes 1/2 hour to do this thing that should take 5 minutes...
Sure, your experience may be different.
That happened in 2013 with random laptop they gave me. I kid you not it took that long, could have been a bug somewhere in the OEM, never cared enough to find out.
But my experience is just as real as much as yours.
I've seen an entire factory shut down for hours because two critical Win10 computers tried and failed to update. It's never an issue until it becomes one.
Plus a failed update is the whole reason I nuked my C: drive and switched to Manjaro (now running Arch, put down the pitchforks).
Ive not had "must update on the spot right this very second," but ive had countless, "we will update the second u power off or attempt a restart. If you try and restart into ur linux partition, we will somehow ensure u fail to boot right up until u got thru with our forced update." Which also sometimes goes hand in hand with, "oops, i was supposed to update, but i shit myself instead. Youre going to need to try again at least once or twice. Dont worry, whether the update goes thru or not, itll only take a maximum of 90 minutes."
Windows can fuck its facehole thru its ass as far as its auto updates are concerned for all i care.