07-22-2020, 09:42 PM
As usual, the InterWeb™ is full of contradictory information. I can't find an authoritative statement for Raspberry Pi OS (aka Raspbian) of the maximum memory space addressable in a 32-bit process (our userland is still 32-bit [1]) running on a 64-bit kernel. However, 3GB is certainly up there and I was keying off the "std::bad-alloc" message.
Were you watching the mem usage? Did it appear that MPD died when the cache was full?
I know this is a heat-it-and-beat-it solution but what happens if you dial the cache size down some and let the system run?
It should be clear I don't understand what the input_cache function really does. The cursory description in the manual doesn't make sense to me now on rereading.
In any case, I don't see the practical benefit of gigabytes of cache given the way we play tracks.
Just my 2 cents worth
Regards,
Kent
[1] In separate effort I'm trying to build moOde in the current beta 64-bit Raspberry Pi OS. It's early days yet.
Were you watching the mem usage? Did it appear that MPD died when the cache was full?
I know this is a heat-it-and-beat-it solution but what happens if you dial the cache size down some and let the system run?
It should be clear I don't understand what the input_cache function really does. The cursory description in the manual doesn't make sense to me now on rereading.
In any case, I don't see the practical benefit of gigabytes of cache given the way we play tracks.
Just my 2 cents worth
Regards,
Kent
[1] In separate effort I'm trying to build moOde in the current beta 64-bit Raspberry Pi OS. It's early days yet.
