logoalt Hacker News

bayindirh • yesterday at 2:53 PM • 3 replies • view on HN

Depends on what low/high end are. If low end is 4 core and deployment is 128 cores, this is not acceptable.

But if low is 64 and high is a whole cluster, now that's a different kind of maths.

Edit: The article states the following:

> "lock contention inside an internal Windows process which caused the machine's resources (CPU & memory) to be exhausted."

So, it's more the former. The testing machine is probably a 8 year old server on an office shelf, and prod machines are 64-128 core cutting edge Xeons/EPYCs.

Lock contention. It was MUTEX spins in Windows 95, it's lock contention in 2026. Why this is still a thing, Microsoft?

(Man, I felt old while writing this.)


Replies

aspbee555 • today at 12:14 AM

I have found that AI really loves using locking/Mutex when working with rust and I have to specifically tell it to not use any locking/use atomics/swaps instead

lokar • yesterday at 3:18 PM

I always this was standard to have a test setup in the production environment on the latest hardware (that’s how you qualified that hardware in the first place) running one “unit” of the system (whatever that is) at full scale and load (ideally higher).

➕ show 1 reply
awesome_dude • yesterday at 11:20 PM

When i saw the lock contention - I immediately thought distributed lock component