BeigeAgenda comments on manyThreadsAreBetterThanOne

[–] BeigeAgenda@lemmy.ca 9 points 2 years ago (2 children)

🤦🏽‍♀️ Thanks for explaining, my brain must have corrected the race condition.

Regarding threads: I have had good experience with using thread safe queues everywhere to exchange data between threads, it's the right tool in many cases, but I doubt queues to be useful when coding for performance.

permalink

fedilink

source

parent

hideshow 4 child comments

[–] expr@programming.dev 1 point 2 years ago (1 child)

Umm, queueing is standard practice particularly when a task is performance intensive and needs limited resources.

Basically any programming language using any kind of asynchronous runtime is using queues in their scheduler, as well.

permalink

fedilink

source

parent

hideshow 2 child comments

[–] BeigeAgenda@lemmy.ca 2 points 2 years ago (1 child)

Could be I was not clear when I wrote performance, I am talking about High Performance Computing, where you want to spend all CPU cycles on solving your problem. While taking Amdal's Law into account. https://en.wikipedia.org/wiki/Amdahl%27s_law

permalink

fedilink

source

parent

hideshow 2 child comments

[–] expr@programming.dev 3 points 2 years ago

Ah gotcha, fair enough. Definitely depends on the workload. If you have compute you want to dedicate to solely to a single task, have at it.

permalink

fedilink

source

parent