4 ms·
Completely agree, i've dealt myself with an access bottleneck as the one he describes. But i found multi-threaded code debugging quite entertaining (sometimes ;
by drtse4 17y ago
Completely agree, i've dealt myself with an access bottleneck as the one he describes.
But i found multi-threaded code debugging quite entertaining (sometimes ;)).
- ajross 17y agoAgreed. Writing low-level synchronization code is hard and error prone. It's almost always worthwhile to burn some extra memory or CPU to choose a solution that's multiprocess instead, or just eat the performance/scalability cost of traditional serialized code. But it's a ton of fun when you get it right. Sort of the "cycle counting" of the modern world.