Hypfer wrote: > It's also 100% not IO related. I've checked that multiple times on > multiple occasions. It's always just one CPU core at 100% actually busy > doing something. Not iowait The point I was making is that if an read/write request (e.g. there are a few cases in LMS code/plugins where such calls are overridden and intercepted before OS) returns 0 bytes rather than ewouldblock - the scheduler select loop would return immediately and be executed repeated - CPU would be 100% and loop and core would not appear to be an a I/O loop. It is a small possibility and has happened occasionally - but perhaps not in this case.
> IO::Socket::SSL: 2.044, but there's no https in this setup 🤔 Version is good. Have you tried the perfwarn command line setting in case it might confirm where the code hot spot is ? ------------------------------------------------------------------------ bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=111312 _______________________________________________ Squeezecenter mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezecenter
