As someone who did that same perf work nah, you really want a good solid implementation if you want to run a reasonable amount of tasks without having workers stall the main thread. You never want the main thread to get blocked and miss a frame because it tried to queue a task.
-
-
The phrase "lock-free" makes it sound like nobody is holding a mutex because they didn't physically issue the mutex in their code. But that is false. The CPU core _is_ taking the mutex, via MESI, unless you are literally talking about instructions that don't use the LOCK prefix.
-
So we need to start understanding that "wait free" is the important thing, and "lock free" is more of a programming fetish thing that doesn't matter in the slightest as far as I've seen.
- Show replies
New conversation -
-
-
This thread show why making a job system using the c++ remind me of scrapyard wars. Tons of stuff, but you have no idea if they will fit or how good they are, or if one has sufficient understanding if it will work.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.