Live data from Hacker News

Did Windows 10 slow down with each feature update?

ntdotdev.wordpress.com

301–310 of 432 posts

Re: Did Windows 10 slow down with each feature update?

#301
post #194

Earlier quoted context omitted.

Where do people even pick this sort of stuff up to take with them into industry? Are they teaching Electron development now in undergrad CSE programs instead of C?

Speaking of C languages C++ still does need more resources to compile programs than AAA games and keep running for 20min / 1h / 2h / 4h? What were they teaching those compilers engineers and language designers back in the day? nothing about writing performant code, performance tests, regressions and yada yada?

This is actually true, LLVM had no performance regression infrastructure until recently, even though it was marketed as the fastest compiler.

C++'s main speed issue is of course that it's the most text-based language ever and many entire libraries are implemented as headers due to the fragile base class issue.

Re: Did Windows 10 slow down with each feature update?

#302
This is great. I would especially love to see some sort of automated testing for this kind of benchmarking across different versions of windows, macos, linux, etc as well. I think it would be incredibly powerful for users to have access to these kind of metrics.

Re: Did Windows 10 slow down with each feature update?

#303
post #230

Earlier quoted context omitted.

I've had massive issues with Ubuntu on a HDD. Every time a big file was added to disk (like a download), the indexing system would run and render the whole system unusable for minutes (100% disk and CPU). Upgrading to an SSD solved the issue.

That's an Ubuntu problem and not an Linux problem thank goodness.

That depends how good Linux's support for very-low-priority background tasks is.

UNIX priorities don't handle this situation well because a low priority process is still technically immediately runnable and can cause priority inversions by clearing out all kinds of system caches that your foreground app was using.

Re: Did Windows 10 slow down with each feature update?

#304
post #199

Earlier quoted context omitted.

All the more reason to install serious ad blockers not found with Chrome and to install extensions that deal with old tabs instead of letting them pollute your memory

I disagree for a few reasons. First, why is the memory limit so low? Like I said, 16gb RAM, yet using just 30% of that total is too much? Secondly, I simply don't believe it is entirely ethical to consume all of the content with none of the ads. I deal with the egregious ad situation by visiting those sites infrequently -- visiting once every few months as opposed to every day, or skipping those links when they appea…

If they want me to view their ads, all they have to do is make them less hostile to me such that they don't get blocked :)

Re: Did Windows 10 slow down with each feature update?

#305
post #261

Earlier quoted context omitted.

>almost innavigable for someone with quick reflexes My few short years with Windows 3.1+ spoiled me for all future versions of windows. Instant closing, instant alt-tabbing, double-clicking the top-left corner icon to close, (nearly) instant opening of simple apps like File Manager and Notepad... not to mention the instant crashes. Linux got close but still always felt clunky, while future versions of Windows and Mac…

That is what I have been banging on about for years . Latency added, not just in Software, but in Hardware as well from Display, Keyboard, Mouse and even Network. The past 20+ years the whole industry nearly went all out on optimising for throughput. Sometimes I look at macOS, Windows 10. Apart from some UI facelift I dont even remember a single user feature that was relevant or important in the past 5 years. Apart f…

You reminded me of "Computer latency: 1977-2017" https://danluu.com/input-lag/

Re: Did Windows 10 slow down with each feature update?

#306

Earlier quoted context omitted.

>almost innavigable for someone with quick reflexes My few short years with Windows 3.1+ spoiled me for all future versions of windows. Instant closing, instant alt-tabbing, double-clicking the top-left corner icon to close, (nearly) instant opening of simple apps like File Manager and Notepad... not to mention the instant crashes. Linux got close but still always felt clunky, while future versions of Windows and Mac…

Right? I opened a Windows XP VM inside my 10 box a bit ago to play an old game, and oh boy was that incredibly snappy compared to what we have now. Sure, it's running in anachronistic hardware, but where did we go wrong? 3.1 was before my time, but I can imagine.

I started with XP with a pentium 2 then move to a pentium 4. It ran perfectly on both. It started even faster than my Linux Mint installation.

Re: Did Windows 10 slow down with each feature update?

#307
Is there even a point to benchmarking boot up time when you can't rely on it being consistent? Sure, it may be thirty seconds ninety percent of the time but the other ten percent it takes ten minutes because it decided installing an update is more important than whatever you wanted to use your computer for. I would never, ever tolerate a Windows 10 machine being the only computer in the house. There's too many times I need something right now and I have to do it with my phone because Microsoft is too busy fellating itself. This problem becomes exponentially worse on any machine that spends most of its time shut down, like a travel laptop.

Re: Did Windows 10 slow down with each feature update?

#308
post #289

Earlier quoted context omitted.

It's my understanding that the bulk of the vulnerabilities in question are not present to near the degree on AMD and ARM. If AMD and ARM could do things mostly properly, why couldn't Intel?

There are a number of the vulnerabilities that affect other platforms than Intel x86 (including some POWER and ARM), though you're correct, a good amount of those disclosed are specific to Intel. But there has also been at least one that was AMD specific, too.[1] I hypothesize it could have come down to "well, we made this type of decision this way before, and the world didn't fall down, so we can probably make it th…

Or simply none of them were aware that the kinds of speculation they were doing were capable of producing exploitable vulnerabilities. It took security researchers a long time to find these issues, and the kind of speculation that the original Spectre and Meltdown exploited were well known outside of the chipmakers for over a decade. Intel was simply more aggressive at that particular avenue of performance improvement.

Re: Did Windows 10 slow down with each feature update?

#309
post #288

Earlier quoted context omitted.

I have never had an issue installing Windows 10 to a machine I upgraded to an ssd…I had hell with an old Dell Precision workstation because of the built in RAID controller…but that’s another story…and when I upgraded that machine to W7 from XP 64 bit, I bought new spinning rust for it. But W8 went smooth and I got W10 working by disabling the RAID during install (I used an SSD for boot). That machine, with dual e5405…

This was the "free" upgrade to 10 from 7. It only offered in-place upgrades. I didn't want to go through the pain of an actual fresh install. I don't really understand why Microsoft couldn't (didn't) give the option to install to a new drive while upgrading.

The upgrade is still free…or at least they still are for me in the US as recently as earlier this year…I have an old Vostro that gets so little use it is faster to reinstall W10 from scratch than upgrade.

The same was true for the old Precision workstation a couple of years ago when I gave it to my kid.

And several other machines including a Win7 Thinkpad off eBay.

My advice is download the installation tool and give it a try.

Backup first as needed of course.

Think of all the complaints Microsoft avoids by keeping Windows 10 available without a bunch of time, money, and rigmarole.

Re: Did Windows 10 slow down with each feature update?

#310

All I know is my Win 10 Pro laptop has 16gb RAM, yet if an application, most likely Google Chrome, uses more than about 4-5gb, it crashes. Yep, it's a lot of tabs. But not as many as you think, and often without warning, as certain ad-heavy sites, especially forum sites (flyertalk, rennlist), can sometimes require 1gb RAM alone.

>yet if an application, most likely Google Chrome, uses more than about 4-5gb, it crashes.

64bit apps shouldn't have such a limit under Windows, and can definitely use more memory. Perhaps you're seeing a case of RAM gone bad (where the large apps are much more likely to trip over the bad location)? Consider running memtest.

Post reply on HN