Skip to content
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

Merged
merged 3 commits into from
Jan 17, 2020

Conversation

julien-f
Copy link
Member

See xoa-support#2075

Check list

Check if done, if not relevant leave unchecked.

  • PR reference the relevant issue (e.g. Fixes #007 or See xoa-support#42)
  • if UI changes, a screenshot has been added to the PR
  • documentation updated
  • CHANGELOG.unreleased.md:
    • enhancement/bug fix entry added
    • list of packages to release updated (${name} v${new version})
  • I have tested added/updated features (and impacted code)

Process

  1. create a PR as soon as possible
  2. mark it as WiP: (Work in Progress) if not ready to be merged
  3. when you want a review, add a reviewer (and only one)
  4. if necessary, update your PR, and re- add a reviewer

From the Four Agreements:

  1. Be impeccable with your word.
  2. Don't take anything personally.
  3. Don't make assumptions.
  4. Always do your best.

@julien-f julien-f requested a review from pdonias January 17, 2020 10:23
packages/xo-server/config.toml Outdated Show resolved Hide resolved
@julien-f julien-f force-pushed the server-configurable-concurrencies branch from dff2109 to 9b1e119 Compare January 17, 2020 10:53
@julien-f julien-f requested a review from pdonias January 17, 2020 10:54
@julien-f julien-f merged commit c7f4648 into master Jan 17, 2020
@julien-f julien-f deleted the server-configurable-concurrencies branch January 17, 2020 12:44
@olivierlambert
Copy link
Member

Should we also update our doc or should we wait for a next release to do so?

@julien-f
Copy link
Member Author

@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 sample.config.toml if they are intended to be changed by users or directly in config.toml if they should probably be left alone.

@olivierlambert
Copy link
Member

olivierlambert commented Jan 17, 2020

okay but we should document our values then (in the config file), to explain why we selected them at the first place.

@julien-f
Copy link
Member Author

@olivierlambert
Copy link
Member

Maybe I'm missing the explanation for vmExportConcurrency = 2?

@julien-f
Copy link
Member Author

See #4742

@olivierlambert
Copy link
Member

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?

@julien-f
Copy link
Member Author

I believe you chose these values, the optimal values probably depend on multiple factors like the XCP-ng/CH version, the SR used, etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants