Change Details

It spent 30ms doing this on startup, now it's like 0.05ms The previous code would assign my quadcore machine that is not hyper-threading capable 8 threads, now it gets 4 instead. I do have the feeling that occasionally the baloo runner blocks the calculator but we need to observe whether this patch makes performance worse but from random testing it doesn't seem like a big deal.

It spent 30ms doing this on startup, now it's like 0.05ms ThreadWeaver has essentially the same logic already. I just set the cap to be /2 of it to keep the old behavior (which I don't know the reason for)

It spent 30ms doing this on startup, now it's like 0.05ms The previous code would assign my quadcore machine that is not hyper-threading capable 8 threads, now it gets 4 insteadThreadWeaver has essentially the same logic already. I do have the feeling that occasionally the baloo runner blocks the calculator but we need to observe whether this patch makes performance worse but from random testing it doesn't seem like a big deal.just set the cap to be /2 of it to keep the old behavior (which I don't know the reason for)