Doesn't matter if i use the original version of trackstat from Erland or
the modified one by myself which prevents duplicate musicbrainz_id.
But as i said. the plugin is according to logs doing nothing.
As you know how to edit the plugin (and you've done so), just add log
statements wherever
bpa wrote:
> Can you clarify the CPU load figure and how many cores on the system.
>
> On some systems with 4 cores if LMS took 100% of a core it could show
> 25% overall but detailed CPU display would show 100% on one core.
>
> Is the 25% on a single core or overall ?
the system has 4
mamema wrote:
> yes, you've said it -> trackstat.
>
> It is/was trackstat. Completely disable this plugin and the CPU load
> from 25% to 2%.
> But! The usual, enable debugging on plugin doesn't help here. As
> trackstat according to the log, does nothing. The plugin is activated,
> but doing
yes, you've said it -> trackstat.
It is/was trackstat. Completely disable this plugin and the CPU load
from 25% to 2%.
But! The usual, enable debugging on plugin doesn't help here. As
trackstat according to the log, does nothing. The plugin is activated,
but doing nothing (according to logs)
As the docker image has no top or htop included, i'm asking here which
debug protocol i should enable to find the culprit?
The "Server information" protocol task doesn't reveal anything
special..
Disabling plugins is always an option to narrow down the culprit. But as
you're working on
As the docker image has no top or htop included, i'm asking here which
debug protocol i should enable to find the culprit?
The "Server information" protocol task doesn't reveal anything
special..
mamema's Profile:
