XenOrchestra multicore ?

akurzawa

Hi

I can observe that during simple task like disk copy xoa user only one cpu - can someone share some details about the design of xoa? can xoa user more cores during some task in parralel?

Also xcp-ng host itself during VM copy from one to host to another:
32 core, 128 ram, 1-core stunnel thread, cpu usage 1,4% - any plans to change the design of coping files(vms) to improve overrall performance?

olivierlambert

Hi,

Feel free to learn a bit about NodeJS main principle: the main event loop: https://nodejs.org/uk/docs/guides/event-loop-timers-and-nexttick/

We added extra threads for merge process (they are doing their work individually).

The idea behind the main event loop is to perform non-blocking I/O at fastest pace possible

edit: also all XO code is open source, take a look there!

olivierlambert

Also ping @julien-f

akurzawa

@olivierlambert

edit: also all XO code is open source, take a look there!

hehe thanks I'll take a look in the five mins:

olivierlambert

good illustration

julien-f

@akurzawa xo-server is not explicitly multi-processed, but it uses async IO calls in Node which should lead to multi-threaded operations.

Anyway, we are currently working on reimplementing backups for the proxy and it will eventually lead to using multiple processes.

These changes will at the end be merged back to xo-server as well.