-
Notifications
You must be signed in to change notification settings - Fork 270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(xo-server/Xapi): make built-in concurrency limits configurable #4743
Conversation
dff2109
to
9b1e119
Compare
Should we also update our doc or should we wait for a next release to do so? |
@olivierlambert These are advanced settings which should probably not be touched by users, unless told to do so by us after analyzing their situation. They may changed or be removed in the future. I don't think we should add them to our documentation, config entries are either documented in |
okay but we should document our values then (in the config file), to explain why we selected them at the first place. |
Maybe I'm missing the explanation for |
See #4742 |
Okay but my original question was about the "why we selected those values" in the first place. I have no memories whatsoever, is a "better" value could be found or we are sure that's the best one? |
I believe you chose these values, the optimal values probably depend on multiple factors like the XCP-ng/CH version, the SR used, etc. |
See xoa-support#2075
Check list
Fixes #007
orSee xoa-support#42
)CHANGELOG.unreleased.md
:${name} v${new version}
)cron/parse.spec.js
)xo-server
API changes, the corresponding test has been added to/updated onxo-server-test
Process
WiP:
(Work in Progress) if not ready to be mergedFrom the Four Agreements: