gstalnaker wrote:
> II didn't want to kill the library scan by restarting LMS.
Why not? At least you can tell if the high cpu usage is caused by the
scanning process. Make some changes in the LMS settings and continu the
scanning ?
-LMS on Raspian Stretch -> 2x Radio
-RPI 3 ('Mopidy' (https://
I did not "know" about the full text search until I did some more
digging. I may do that. I also learned about cgroups as part of my
research. cpulimit is really for already running processes, which is why
I tried using that. I didn't want to kill the library scan by restarting
LMS.
Roland0 wrote
Mnyb -- Yes, it is a new install and yes it is a big collection on a
network share and yes I can just wait.
But seems to me, I can be wrong, that with three processes running, only
one of which is the scanning/index building, that they can be
architected/run in such a way as to make LMS available
Try disabling the full text search plugin.
If you want to limit cpu, use 'cgroups'
(http://www.fernandoalmeida.net/blog/how-to-limit-cpu-and-memory-usage-with-cgroups-on-debian-ubuntu/)
SW: 'Web UI for LMS'
(http://forums.slimdevices.com/showthread.php?98186-Announce-Alternative-Web-Interface-(
gstalnaker wrote:
> Putting the scanning process, which has been "building the index" for 95
> minutes now, on 50% CPU and renicing it back to 0, and putting the main
> LMS to 80% CPU has not made connecting to LMS possible :-)
Why didnt you use the builtin performance settings from lms instead o
Is this new install ? Just wait untill the initial scan is finished .
Is it a big collection ?
Local USB disc or is the music on a network share ?
Main hifi: Touch + CIA PS +MeridianG68J MeridianHD621 MeridianG98DH 2 x
Meri
Putting the scanning process, which has been "building the index" for 95
minutes now, on 50% CPU and renicing it back to 0, and putting the main
LMS to 80% CPU has not made connecting to LMS possible :-)
gstalnaker's Profil
https://www.tecmint.com/limit-cpu-usage-of-a-process-in-linux-with-cpulimit-tool/
Can be used to modify CPU usage of a *running* process. Can only be used
from a terminal session. Is not permanent. But if you encounter a
situation like mine where LMS is basically useless, you can affect how
LSM a
While renice does modify the priority it does not modify CPU use. And
though I was able to connect to the LMS web UI after its CPU use fell,
the minute I clicked on anything in the UI to "show" content, its CPU
shot back up to 100% and now I cannot connect again.
So it's not just priority. On a R
One can use at the CLI:
#> ps -ef | grep squee
to see list of the processes that include "squee" which will show the
primary LMS processes and the Scanning process if running. Note the
Proccess ID (PID) of the scanning process. In my output from earlier:
squeeze+ *1480* 396 34 00:16 ? 00:29:53
The system is functional. I have connectivity via ssh right now (where
some of the following comes from) and can see SqueezeBox* processes
running:
lms_raspberrypi% ps -ef |grep squee
squeeze+ 385 1 0 Feb14 ?00:00:00 /bin/bash
/usr/sbin/squeezeboxserver_safe /usr/sbin/squeezeboxser
11 matches
Mail list logo
