Closed bartmans closed 1 year ago
I added: environment:
This made the environment a bit more responsive. Library scan now finishes but still Airsonic is unresponsive while scanning. I would say that this image needs more system (cpu, memory) than the 'old' image). I am using a Synology 720+ (Intel Celeron J4125 4-core 2.0 GHz) with 8GB.
I read your post on your roadmap for this fork. Maybe spend some time on optimizations to speed things up on lowerend hardware? If I am not the only one of course.
@bartmans Thank you. You are right! I will work on it.
FYI:
If you don't set Fast access mode
, you should.
It makes performance better.
First of all: a big thank you for taking this on! It would be a shame if Airsonic wasn't kept up to date. I am definitely not a programmer, but if I can help in anyway (testing?) I will.
And a big difference indeed in memory use between Java 11 en 17:
11.0.0-SNAPSHOT.20230217142243 – 17 februari 2023 om 15:22:43 CET [Commit: 1397446f979b1cdea283eec89ce4f0eae7d63450] Server Apache Tomcat/9.0.60, java 11.0.18, Linux (276,1 MB / 512,0 MB)
11.0.2-SNAPSHOT.20230227155658 – 27 februari 2023 om 16:56:58 CET [Commit: adbc2cfc9c56d1a70b5d9e3cc05e8a96658dd5f2] Server Apache Tomcat/9.0.70, java 17.0.5, Linux (364,0 MB / 1,07 GB)
@bartmans
thank you for information.
Besides the Java version, there are several differences between 11.0.0 and latest version.
I built latest version by java 11.
ghcr.io/kagemomiji/airsonic-advanced:pr-132
Could you try it and check memory usage?
Server | Apache Tomcat/9.0.70, java 11.0.18, Linux (436,4 MB / 825,0 MB)
It's not memory usage. I tried:
Logged in, ticked 'fast access' and let libraries scan. After the first time, turned off full library updates and ran the scan again.
AA took under 2 minutes to update library. PR-132 is still busy after > 30 minutes. Performance for both instances is otherwise good: tried with multiple clients, simultaneous streaming, no problem.
So maybe it has more to do with disk access? And am curious if I am the only one with this performance issue.
@bartmans Thank you for trying PR-132.
So maybe it has more to do with disk access?
Yes, latest edge version has more disk access than latest AA, because latest edge version supports cue sheet file. Next, I will look at disk access and optimize it.
And am curious if I am the only one with this performance issue.
I also think this is problem. I want to fix it.
Yeah you did it! Nice: 2023-03-05 18:32:19.473 INFO --- o.a.p.s.MediaScannerService : Media library scan took 102s
Thank you.
What happened?
Using airsonic-advanced-latest until now. Wanted to use the new Dockerimage from here.
First copied the folder and installed from Docker Compose. Airsonic came up without a problem with all my settings. When indexing Airsonic slowed down and ultimately crashed. Library consists of 97000 mp3s.
When restarting Airsonic crashed.
I then started fresh, without existing configuration. Same problem. At the top Airsonic used almost 5GB of memory during indexing the library.
Steps to reproduce
Fresh install on Synology with latest image
Start indexing library
Wait long enough, around the 65000 mp3's it slows to a crawl, then stops.
Version
11.0.2 (Stable)
Version Detail
No response
Operating System
Synology Docker
Java Version
17
Database
Other
DB Detail
sqlite
Configuration paramter
version: "2.1" services: airsonic-advanced: image: ghcr.io/kagemomiji/airsonic-advanced:latest container_name: airsonic-advanced-kagemomiji environment:
PUID=1026
PGID=100
TZ=Europe/Amsterdam volumes:
/volume1/docker/airsonic-advanced-kagemomiji/config:/config
/volume1/docker/airsonic-advanced-kagemomiji/airsonic:/var/airsonic
/volume1/docker/airsonic-advanced-kagemomiji/playlists:/playlists
/volume1/docker/airsonic-advanced-kagemomiji/podcasts:/podcasts
/volume1/music:/music ports:
4041:4040 restart: unless-stopped
Proxy Server
Nginx
client detail
All
language
Dutch
Relevant log output