One thing to note is that the nice level of the replaygain analysis is set
so that that it has low CPU scheduling priority, while the Liquidsoap
process is given high scheduling priority.
This replaygain analysis is done ahead of time, and once all tracks in the
library have been analysed, it should never become a problem again. From
the command line we can run
sudo -u postgres psql -c 'SELECT count(*) FROM cc_files WHERE replay_gain
IS NULL;' airtime
If the print value is zero, this means that no more replaygain analysis is
happening (unless more track are added of course) and therefore is not the
problem.
At the moment all signs still point to Apache CPU usage spike as the
culprit.
------------------------------------------------------------------------------
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users
