Comment Comment by ko27 I think the argument against thread-per-core as the default can be made simply:- if you are CPU bound, work stealing will be better for most cases- if you are IO bound, thread-per-core might work better, but again, you have enough CPU headroom that the performance doesn't really matterIMO, work stealing is a better default to encode into language API parent ko27 3 years ago
- if you are CPU bound, work stealing will be better for most cases
- if you are IO bound, thread-per-core might work better, but again, you have enough CPU headroom that the performance doesn't really matter
IMO, work stealing is a better default to encode into language API