PicorePlayer LMS Media scan terminated unexpectedly and then rescans randomly

[mherger]

> Could you please let me know where to check the size of the DB? I could
> check the size tonight and then post it here.

It's in the cache folder. See Settings/Information in LMS.

--

Michael

[bpa]

if the PI four would be of advantage here.

Pi4 has faster processor, better network and USB interfaces - so performance should improve.

You should check on the PCP thread but IIRC I think because of 32 bit legacy (which may change) LMS cannot use more than 2Gb.

So on a pure LMS/PCP no point to 8Gb or possibly 4Gb. However transcoding applications use non LMS memory so if doing a lot of transcoding (e.g. Chromecast, UPNP bridges) - memory might help.

You may have other considerations (e.g. plans to run LMS + other application on 64 bit Raspbian) whee additional memory could be useful.

[mherger]

> You should check on the PCP thread but IIRC I think because of 32 bit
> legacy (which may change) LMS cannot use more than 2Gb.

2GB is already twice the 1GB of a Pi3 - which is a lot more ;-).

> So on a pure LMS/PCP no point to 8Gb or possibly 4Gb.

Would the 2GB limit be per process or overall? During the scan LMS runs
two processes. In that case the scanner could probably take advantage of
a full 2GB instead of a few hundred MB with a Pi3?

--

Michael

[Pommes]

I will observe my existing PI three, and check if it is running stable. A full rescan is not necessary very often, and I like the fact that the PI three uses less energy than the PI four, but if there should be any problems again, I think I might buy a PI four.
Thank you
Pommes

[mherger]

> I will observe my existing PI three, and check if it is running stable.
> A full rescan is not necessary very often, and I like the fact that the
> PI three uses less energy than the PI four, but if there should be any
> problems again, I think I might buy a PI four.

Could you please still tell me the size of your library.db? Maybe I can
do something on the software side to prevent the crash.

--

Michael

[bpa]

I forgot Pi3 was only 1Gb.

Would the 2GB limit be per process or overall?

I don't use PCP (yet), so my "advice" was based on what I think I read in pcp threads.

I think there are two issues - Perl pointers (check using perl -Vtrsize ) and 64 bit OS kernel address.
Multiple process will share the memory that is accessible to the kernel but most of the time LMS is one process managing many players.

If user does not already have a Pi3B+, it is worth going for Pi 4 2GB over a Pi 3 with 1Gb as they are same price and there'll better performance.

If a user already has a Pi3B+, is it worthwhile upgrading to a Pi4 ? Possibly - especially if large file collection, maybe not if mainly internet streaming.
If user is "price sensitive" - is it worthwhile to go for 4GB as 4Gb vs 2Gb is €60 vs €38. - not sure but maybe future proofing.

[Paul Webster]

Just for comparison ... mine (which scans without a problem on a Raspberry Pi 3 Model B Rev 1.2 with 1GB memory)

537112576 Dec 18 09:59 /usr/local/slimserver/Cache/cache.db
 36725760 Dec 18 10:10 /usr/local/slimserver/Cache/persist.db
143614976 Dec 18 10:10 /usr/local/slimserver/Cache/library.db

[mherger]

> 143614976 Dec 18 10:10 /usr/local/slimserver/Cache/library.db

How many tracks would that be?

--

Michael

[Paul Webster]

Just under 100k
Slightly special case though as many are the result of .cue files splitting multi-hour radio shows into tracks.

[Pommes]

> I will observe my existing PI three, and check if it is running stable.
> A full rescan is not necessary very often, and I like the fact that the
> PI three uses less energy than the PI four, but if there should be any
> problems again, I think I might buy a PI four.

Could you please still tell me the size of your library.db? Maybe I can
do something on the software side to prevent the crash.

--

Michael

du -h library.db
357.6M library.db

Pommes