Hacker News
new
|
past
|
comments
|
ask
|
show
|
jobs
|
submit
login
Jare
on Aug 7, 2014
|
parent
|
context
|
favorite
| on:
Go 1.4+ Garbage Collection Plan and Roadmap
I took it to mean he launched several copies of the process, each copy pinned to one (and only one) core.
kator
on Aug 8, 2014
[–]
Correct it was the only way to get Go to scale to a reasonable response rate for this application and it thus meant my CPU loading was not even since it was based on the randomness of socket connections that persisted on one cpu or another.
Guidelines
|
FAQ
|
Lists
|
API
|
Security
|
Legal
|
Apply to YC
|
Contact
Search:
