Energy and resource efficiency on a NAS Storage

[StarPicard]

Hello, first of all, thank you for this great project! I really use ABS every day and benefit a lot from it.

Since I am now moving ABS to new hardware, I would be happy to discuss with you suggestions on how to make ABS more resource and energy efficient.

I think it makes sense to describe my setup first of all. I have hosted ABS as a Docker image. The metadata and configurations are mounted on an SSD. The actual audio books are on HDDs, which go into standby whenever possible.

Now I have noticed that the HDDs also start up when I only call up the ABS web interface. However, this should not actually happen as, in my understanding, the covers are in the Metadata folder. Does anyone here have any ideas as to which accesses to the actual audio books could be waking up my HDD?

The second part of the discussion would be my idea of adding a function to copy the audiobooks I have just listened to into a “cache” folder, which can then be mounted on the SSD via Docker if required. This would have the advantage of not always having to access the HDD when continuously listening to an audiobook, but would still save storage space on the SSD. I am aware that the idea may be a special case, but perhaps more people would benefit from the idea.

Do you have any other ideas for making Audiobookshelf more efficient?

[nichwall]

Not sure what would be accessing the HDDs if you have everything (database and metadata folders) on SSD. Maybe if you have the watcher enabled it will be monitoring the HDD?

I have read online that people using Docker on their NAS causes HDD to not sleep (probably due to logging or something?), but not sure if that applies here.