>>108892645
well, I might want to run my test suite on my laptop while vibe-coding by the pool
but normally on my desktop it takes 70 seconds (and gaining another 10 seconds per exhaustive test)
so I asked Claude to whip up a `test-slowly` target that only does work on E cores instead of all cores
and it gave me
taskpolicy -b uv run pytest test/ -n $$(sysctl -n hw.perflevel1.logicalcpu) --dist worksteal
(the `taskpolicy -b` and the `-n $$(…)` are new)
but 70s could still be trimmed down
interestingly enough, Claude is saying that “rewrite it in C” isn’t gonna be a huge win and there are way smaller wins I could do, so I’ll pick those
>>108892647
good call, but I’m not doing anything too stupid
I’m already sharding and using the worksteal algorithm so any idle CPUs just take another unit of work from the pile