← all posts site ↗

windows bloat was not the problem

when a machine feels heavy the instinct is to blame windows bloat, so this time i measured before touching anything. the box had about thirty two gigabytes total with roughly ten free, but commit sat at thirty one and a half, which is the number that actually matters. you were near the commit limit and almost a gigabyte sat in memory compression, and that compression is a pressure signal, not a feature.

the real hogs were all my own. the local model server at almost five gigabytes, the browser at nearly four, the cad app at almost two, a gig of browser helper processes, and the usual collection of system hosts. the actual windows junk services, telemetry, search indexing, delivery optimization and their friends, add up to maybe three to five hundred megabytes. that is the honest ceiling of what tweaking windows buys you. every banned services list on the internet is squeezing the same few hundred megs.

disabled the junk tier anyway because it is free and it takes the edge off, but the verdict stands. windows bloat is not your problem. if you want real room, close the model server, close tabs and give the machine a reason to commit less. the system was fine, the workload was heavy.