XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    XOA High CPU / Single Core

    Scheduled Pinned Locked Moved Xen Orchestra
    7 Posts 2 Posters 849 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • K Offline
      KernelCrunch
      last edited by

      I'm getting occasional alerts, through out the day, on my XOA VM for 90%+ CPU. It appears to be a single core that's going nuts. (Is XOA single threaded?). This is on a AMD Ryzen 3900X CPU. The pool has 40 Active VMs (across multiple servers).

      Could this be a configuration issue?

      I increased the RAM from 4GB to 6GB. Maybe more would help?

      Not really an issue, but probably something worth investigating.

      XOA Chart.png

      1 Reply Last reply Reply Quote 0
      • olivierlambertO Online
        olivierlambert Vates 🪐 Co-Founder CEO
        last edited by

        XO is build on using NodeJS. It's fast to do I/O because it's using an event loop (see https://nodejs.org/en/docs/guides/event-loop-timers-and-nexttick/ )

        We are using workers for some tasks (backup merge) but most of the task are in a single process.

        Also in your screenshot, there's a lot of traffic going on, so it might happen during a backup

        1 Reply Last reply Reply Quote 0
        • K Offline
          KernelCrunch
          last edited by

          Yes, definitely a backup running. I find XOA borderline unusable when I'm running backups, it doesn't matter how much horsepower I throw at it.

          I would set up a proxy, but this is in my (high-end but still coming out of my pocket) home-lab.

          Annotation 2020-08-21 011354.png

          K 1 Reply Last reply Reply Quote 0
          • K Offline
            KernelCrunch @KernelCrunch
            last edited by KernelCrunch

            Unusable is going too far. Noticeably slow, yes.

            1 Reply Last reply Reply Quote 0
            • olivierlambertO Online
              olivierlambert Vates 🪐 Co-Founder CEO
              last edited by

              This will be far better in few releases 🙂 When new backup code used in the proxy will be merged into main XO code (so it won't block the event loop)

              1 Reply Last reply Reply Quote 1
              • K Offline
                KernelCrunch
                last edited by

                Side note:

                My bad. I built mine from source, so I should be referring to it as 'XO', not 'XOA'.

                1 Reply Last reply Reply Quote 0
                • olivierlambertO Online
                  olivierlambert Vates 🪐 Co-Founder CEO
                  last edited by olivierlambert

                  No problem 🙂 Proxy code will help a lot when merged in your main XO!

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post