Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Slow web gui
#1
Next track: audio switches instantly, but gui updates like 5 seconds after that. Sometimes never updates. What can cause this? Rpi3B, link 50/70, signal strength is -60db
Another one problem, if I do not close moode tab on phone, next time opening new tab takes longer and longer, some times gray screen. If i close all other tabs on all devices, feels a bit faster and responsive.
Reply
#2
The symptoms suggest a network issue or some other resource issue external to moode software.

To start troubleshooting do the following:

Reboot and then post the contents of the startup log.
The log can be viewed via the SSH command moodeutl -l or downloaded via the Logs section in System Config, or via Menu, System info from any of the Config screens. The startup log will be at the end of System info output.
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#3
I had this problem with my tablet for quite a while. I bought one with more ram and a somewhat faster processor and got acceptable response time. The one that works has 6 GB RAM and a Media-Tek Helio G90T (Octa-Core, 2x A76 @2.05GHz + 6x A55 @2.0GHz) processor. One thing I checked before upgrading was the wifi signal strength in the places I normally used the tablet.
Reply
#4
Which web browser are you using?

Even with the content blockers/filters turned off for Moode, it's still quite sluggish on Safari on an M1 MacBook Pro and also on an iPhone SE (gen 3). This is regardless of having LazyLoad enabled or disabled in the Moode preferences page.

But on a cheap Intel N100 mini PC with Firefox, it runs much better.

They both have a good wifi connection. The Pi running Moode is wired directly to the router using ethernet.

I might see if Firefox on the M1 works any better actually.
Reply
#5
I just tested it with the latest version of Firefox on the M1. And it is definitely more snappier.

I think there's something about the underlying rendering software of the iThings which don't seem to work as well as whatever Firefox is using.

So test with different browsers and see if you notice any improvements. Make sure things like ad filters/content blockers are disabled, you don't need them for Moode and they may add extra latency.
Reply
#6
(08-09-2024, 03:54 PM)Always_In_The_Moode Wrote: Which web browser are you using?

Even with the content blockers/filters turned off for Moode, it's still quite sluggish on Safari on an M1 MacBook Pro and also on an iPhone SE (gen 3). This is regardless of having LazyLoad enabled or disabled in the Moode preferences page.

But on a cheap Intel N100 mini PC with Firefox, it runs much better.

They both have a good wifi connection. The Pi running Moode is wired directly to the router using ethernet.

I might see if Firefox on the M1 works any better actually.

Very odd. On my iMac and iPhone WebUI performance is super fast on all 7 of my Pis (Pi3//4/5) 
- Tested on iMac using Chrome, Safari or Firefox
- Tested on iPhone using Chrome, Safari

WebUI performance can be affected by slow network, NAS, local disk, or really huge collection.

You should try to isolate the bottleneck.
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#7
Hi Tim,

I have a grand total of 10786 tracks in the playlist right now. Would that count as a really huge collection? The NAS contains a huge collection for sure too.

Maybe I should temporarily test a smaller playlist and see how that pans out?
Reply
#8
Thats a ginormous playlist. If you are using it to do random play I would switch to using Auto-shuffle It only ever adds two tracks to the playlist (in Track mode).

How many tracks in your collection?
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#9
Looks same with all browser and client devices.
Got big collection like 2tb of music on 70mb/s nas hdd. Can this cause issues? Got slow library loading but it is okay.
Playlist was just three flac albums.
Overall web perfomance looks slow
Reply
#10
I have 1300 albums, totaling almost 16500 tracks, and performance is wonderful.
Although I do not have actually 16k files to scan... I have whole-albums FLACs + CUE.
I do not think this makes a difference, database-wise, but it could... it definitely doesn't when it comes to the front-end receiving its library JSON file, though.
Reply


Forum Jump: