Auto-scaling will 'never' perform better than fixed one. At best perform equal I guess (e.g. compare std::vector to normal arrays)
On Thursday, May 8, 2014 5:42:35 PM UTC+2, Ben Noordhuis wrote: > > On Thu, May 8, 2014 at 10:26 AM, Kees k <[email protected]<javascript:>> > wrote: > > Why the pool size is 4; is it a pragmatic choice? > > More or less. The actual number is fairly arbitrary but the reason > it's fixed is that I couldn't make an auto-scaling thread pool always > perform better than a fixed one. I've tried several approaches but > they all regress some of the benchmarks. > -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/4b0e8b34-7272-488d-8507-29c090970b89%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
