Or they could have originally defaulted to GOMAXPROCS=2 to uncover these races w... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

cpeterso on May 28, 2015 | parent | context | favorite | on: Go 1.5 max procs default

Or they could have originally defaulted to GOMAXPROCS=2 to uncover these races while still minimizing the problems from their gorountine scheduler.

pcwalton on May 29, 2015 | [–]

GOMAXPROCS=2 wouldn't make things better, since the Go runtime has all sorts of special cases to handle GOMAXPROCS=1 that don't kick in with any higher value (in particular, removing locks).

andy_boot on May 28, 2015 | [–]

that to me looks like the worst of both worlds.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact