Thanks for your pull request.

It looks like this may be your first contribution to a Google open source project, in which case you'll need to sign a Contributor License Agreement (CLA) at https://cla.developers.google.com/.

If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check the information on your CLA or see this help article on setting the email on your git commits.

Once you've done that, please reply here to let us know. If you signed the CLA as a corporation, please let us know the company's name.

We should probably hold off on adding parallelizing optimizations to the APIserver until we have consistently run the existing apiserver code with multiple threads. AFAICS, we don't set GOMAXPROCS for apiserver.

As per #4521 we're setting GOMAXPROCS now. But I agree that we should hold this change until we know how APIserver works in multithreaded environment.

gmarek what is the status on this?

@gmarek

That I don't know. I wrote this in hope that it'll speed up APIserver, but gains are not very big. The side effect that I didn't fix in this PR is that ordering of the output is not deterministic anymore. There'll need to be some kind of sorting somewhere later in the code path. I'll do it, if you think this PR makes sense, as a part or general parallelization of Kubernetes. If not, we can just drop it.

I don't think this makes sense at this time if the wins are not big.