Expose cpu quota

[ovesh]

This PR exposes the api for querying the cpu quota.

The specific use case is when we need to specify the concurrency level (via cli arg) for a non-golang subprocess.

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 4 lines in your changes missing coverage. Please review.

Project coverage is 90.09%. Comparing base (e393bb0) to head (5f4d8ed).
Report is 37 commits behind head on master.

Files with missing lines	Patch %	Lines
cpuquota/cpuquota.go	0.00%	4 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master      #28      +/-   ##
==========================================
- Coverage   91.91%   90.09%   -1.83%     
==========================================
  Files           8        9       +1     
  Lines         198      202       +4     
==========================================
  Hits          182      182              
- Misses         13       17       +4     
  Partials        3        3              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[jcorbin]

Would your use case be able to instead just use runtime.GOMAXPROCS(-1) to get the effective value separately from this library?

[ovesh]

Would your use case be able to instead just use runtime.GOMAXPROCS(-1) to get the effective value separately from this library?

@jcorbin
To my understanding, no. runtime.GOMAXPROCS(-1) won't return an accurate CPU allocation for a containerized application. It returns the global runtime.gomaxprocs, which I verified is the total number of cores on the host and not the CPU allocation.

Am I misunderstanding your comment?

[jcorbin]

Would your use case be able to instead just use runtime.GOMAXPROCS(-1) to get the effective value separately from this library?

@jcorbin
To my understanding, no. runtime.GOMAXPROCS(-1) won't return an accurate CPU allocation for a containerized application. It returns the global runtime.gomaxprocs, which I verified is the total number of cores on the host and not the CPU allocation.

Am I misunderstanding your comment?

So our automaxprocs library works be changing that value. Any time after that, you'll get the newly affected value ( unless something else has changed it of course, which should be rare ). It adds a little bit of logic like "round down" and minimum clamping. But it will be better than the total number of cores available.

[ovesh]

So our automaxprocs library works be changing that value

I'd like to get the value without setting it for the current process.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Avishai Weissberg seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[piyush-singh]

This PR would resolve #29 which would be useful for us here at cockroach. Any chance we can revive this?

[prashantv]

Please see my comment here: #29 (comment)