From: usenet.16@scottsonline.org.uk.invalid   
      
   An oddity, although resolved for now.   
      
   On a new low-power machine, intended ultimately as headless. When I   
   logged in over ssh and ran top, I saw pipewire taking a steady perhaps   
   15% cpu: I replaced with pulse, and pulse instead took 20% or so.   
      
   In either case, and still running top on the ssh session, simply logging   
   on on the console made this drop virtually to 0%.   
      
   I've resolved the issue by removing pipewire and disabling pulse with   
   systemctl, which is OK as I don't need audio for this box at all.   
      
   But I'd love to know what's been going on. Can anyone shed light please?   
      
      
   --   
   Mike Scott   
   Harlow, England   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)