alphacyberranger@sh.itjust.works to Programmer Humor@lemmy.mlEnglish · 7 months agomanyThreadsAreBetterThanOnesh.itjust.worksimagemessage-square39fedilinkarrow-up1731arrow-down138
arrow-up1693arrow-down1imagemanyThreadsAreBetterThanOnesh.itjust.worksalphacyberranger@sh.itjust.works to Programmer Humor@lemmy.mlEnglish · 7 months agomessage-square39fedilink
minus-squareexpr@programming.devlinkfedilinkarrow-up1·7 months agoUmm, 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.
minus-squareBeigeAgenda@lemmy.calinkfedilinkarrow-up2·7 months agoCould 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’s_law
minus-squareexpr@programming.devlinkfedilinkarrow-up3·7 months agoAh 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.
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.
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’s_law
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.