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

xo-server splitting #2948

Closed
4 of 9 tasks
julien-f opened this issue May 15, 2018 · 2 comments
Closed
4 of 9 tasks

xo-server splitting #2948

julien-f opened this issue May 15, 2018 · 2 comments

Comments

@julien-f
Copy link
Member

julien-f commented May 15, 2018

Why?

  • performance: move CPU intensive work in dedicated processes
  • memory: isolate potential leaks to make them easier to diagnose
  • memory 2: mitigate Node 2GB limit
  • safety: isolate different parts of code to limit process failures impact
  • maintenance: improve code quality by separating concerns

Lightweight stuff (only IO)

Handled directly by the front-end process

  • HTTP file serving
  • WebSocket API
  • WebSocket-TCP console proxy

Services

Should be handled by dedicated workers.

  • DB
  • connections to XAPI (each in a worker)
  • XAPI stats

Tasks

Should be handled by generic workers.

  • backupVm
  • mergeVhd
  • createSyntheticVhdStream
@julien-f
Copy link
Member Author

To do after backup proxies.

@julien-f
Copy link
Member Author

julien-f commented Apr 7, 2020

This will come progressively thanks to the work on XO proxy.

@julien-f julien-f closed this as completed Apr 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant