DocMarty84
commented
6 years ago Hum, how "slow" is your installation in comparison with the demo server? It is seems much slower, there might be a few things to improve.
First, what are the parameters assigned to the VM? I would recommand at least 2 CPUs to take advantage of the parallelization of the requests. Note that even if you assigned only 1 CPU, you might give a shot to this:
- stop the service:
systemctl stop koozic@root.service - disable the service:
systemctl disable koozic@root.service - Open the file
/etc/systemd/system/koozic@.serviceand edit the line 'ExecStart..' to be:ExecStart=/opt/koozic/odoo-bin -d koozic --workers=2 --limit-time-cpu=1800 --limit-time-real=3600 - enable the service:
systemctl enable koozic@root.service - start the service:
systemctl start koozic@root.service
This will enable the use of 2 processes (workers). You might as well try 4 since Koozic is the "only" service running on your VM.
Moreover, there are a couple of background jobs that might be running. These might kill the performances if only 1 CPU/worker is used. Indeed, your collection being huge, they take some time to run and some of them are resource hungry:
- create the image cache: it is used to pre-compute all the thumbnails.
- create the LastFM cache: it prefetches all artist information from LastFM
You might want to run these at night, or completely deactivate them.
- Activate the debug mode (url: http://_hostname_:8069/web?debug)
- Go to Settings > Automation > Scheduled Actions
In the list, some of them start with "oomusic...". You can set a "Next Execution Date" at night (if your VM runs 24/7), or change the frequency (once a week/month instead of once a day), or even deactivate them (untick the "Active" field).
The drawback of deactivation is that what was not computed by these scheduled actions might need to be computed on-the-fly when necessary. For example, if you open the details of an artist and the corresponding LastFM information have never been fetched before, it might take a few seconds before the page opens (just the time to fetch the data). Once the data is fetched, that's kept in cache for some time. So, it's only the first access which is slow. Further accesses won't be.
You can also go to Settings > Parameters > System Parameters, and change the value of "oomusic.lastfm_cache_duration" to 90 or more. LastFM info will be updated every 90 days (or more) instead of 14.
That would be nice if you could give a shot to this. It you can witness a noticeable improvement, I will adapt the default set-up to fit with a huge database.
Finally, I agree that the interface is not super-smooth, even with a perfectly configured system. That's inherent to the development framework used (Odoo).
aroundmyroom
I see that python /opt/koozic/odoo-bin is rather using a lot of CPU where I think: you do nothing. ;_) also with my large db and running in the VM that builing up a page takes some time
I'll keep watching the development as right now next to subsonic its the best alternative, but I do miss the feeling that it is smooth and slack when pressing songs etc.