Category Archives: Performance

Reflections on My Tech Career – Part 2

Posted on November 10, 2025 by brucedawson

This is second and final part of the story of how my career as a software developer unfolded (part 1 is here). In this half I work at four different companies in the Seattle area, make my mark, and then … Continue reading →

Posted in Bugs, Chromium, Floating Point, Investigative Reporting, Linux, Performance, Programming, Quadratic, Symbols, uiforetw, Unicycling, Xbox 360, xperf | Tagged , , , , , | 20 Comments

Acronis True Image Costs Performance When Not Used

Posted on May 26, 2025 by brucedawson

Over two years ago I installed Acronis True Image for Crucial in order to migrate my data to a new SSD I had just purchased. It worked. I then left True Image installed “just in case”, and what harm could … Continue reading →

Posted in Investigative Reporting, Performance, uiforetw, xperf | Tagged , , | 17 Comments

32 MiB Working Sets on a 64 GiB machine

Posted on October 1, 2023 by brucedawson

Memory is a relatively scarce resource on many consumer computers, so a feature to limit how much memory a process uses seems like a good idea, and Microsoft did indeed implement such a feature. However: They didn’t document this (!) … Continue reading →

Posted in Computers and Internet, Investigative Reporting, memory, Performance, Programming, uiforetw, xperf | Tagged , , | 10 Comments

No Start Menu for You

Posted on January 17, 2023 by brucedawson

I tend to launch most programs on my Windows 10 laptop by typing the <Win> key, then a few letters of the program name, and then hitting enter. On my powerful laptop (SSD and 32 GB of RAM) this process … Continue reading →

Posted in Code Reliability, Debugging, Investigative Reporting, Performance, Programming, Rants, uiforetw, xperf | Tagged , , | 28 Comments

Why Modern Software is Slow–Windows Voice Recorder

Posted on September 29, 2022 by brucedawson

I apologize for this title because there are many things that can make modern software slow. Blindly applying one explanation without a bit of investigation is the software equivalent of a cargo cult. That said, this post describes one example … Continue reading →

Posted in Investigative Reporting, Performance, uiforetw, xperf | Tagged , , | 41 Comments

Slower Memory Zeroing Through Parallelism

Posted on July 11, 2022 by brucedawson

While investigating some performance mysteries in Chrome I discovered that Microsoft had parallelized how they zero memory, and in some cases this was making it a lot slower. This slowdown may be mitigated in Windows 11 but in the latest … Continue reading →

Posted in Investigative Reporting, Performance, uiforetw | Tagged , | 13 Comments

11 mm in 1.25 nanoseconds

Posted on January 12, 2022 by brucedawson

In 2004 I was working for Microsoft in the Xbox group, and a new console was being created. I got a copy of the detailed descriptions of the Xbox 360 CPU and I read it through multiple times and suddenly … Continue reading →

Posted in Fun, Performance, Xbox 360 | Tagged , , | 14 Comments

Arranging Invisible Icons in Quadratic Time

Posted on February 16, 2021 by brucedawson

Near the end of January I was pointed to a twitter thread where a Windows user with a powerful machine was hitting random hangs in explorer. Lots of unscientific theories were being proposed. I don’t generally do random analysis of … Continue reading →

Posted in Investigative Reporting, Performance, Programming, Quadratic, Rants, Symbols | Tagged , | 21 Comments

Windows Timer Resolution: The Great Rule Change

Posted on October 4, 2020 by brucedawson

The behavior of the Windows scheduler changed significantly in Windows 10 2004 (aka, the April 2020 version of Windows), in a way that will break a few applications, and there appears to have been no announcement, and the documentation has … Continue reading →

Posted in Environment, Investigative Reporting, Performance, Rants | Tagged , | 106 Comments

The Easy Ones – Three Bugs Hiding in the Open

Posted on August 30, 2020 by brucedawson

I write a lot about investigations into tricky bugs – CPU defects, kernel bugs, transient 4-GB memory allocations – but most bugs are not that esoteric. Sometimes tracking down a bug is as simple as paying attention to server dashboards, … Continue reading →

Posted in Bugs, Code analysis, Code Reliability, Debugging, Floating Point, Linux, Performance | Tagged | 17 Comments