Thank you for your donation!


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


Solved: Large library - performance (5.3 VS 4.4)
#21
(06-07-2019, 04:13 PM)Just tried to apply the patches.  The wget failed with a 404 error.  I tried it with ssh on a pi and also tried the http portion from a browser on my desktop machine.   Tim Curtis Wrote: Here are the lazyload patches :-)

Code:
wget http://moodeaudio.org/test/lazyload-update.zip
unzip -q ./lazyload-update.zip
sudo mv ./playerlib.js /var/www/js
sudo mv ./scripts-panels.js /var/www/js
sudo rm ./lazyload*

-Tim
Reply
#22
(06-15-2019, 07:12 PM)Just to clarify, h ere\s the output of the wget from the pi: Wrote: pi@moode:~ $ wget http://moodeaudio.org/test/lazyload-update.zip
--2019-06-15 12:15:29--  http://moodeaudio.org/test/lazyload-update.zip
Resolving moodeaudio.org (moodeaudio.org)... 23.235.199.139
Connecting to moodeaudio.org (moodeaudio.org)|23.235.199.139|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2019-06-15 12:15:29 ERROR 404: Not Found.





nosferatu_cat
(06-07-2019, 04:13 PM)Just tried to apply the patches.  The wget failed with a 404 error.  I tried it with ssh on a pi and also tried the http portion from a browser on my desktop machine.   Tim Curtis Wrote: Here are the lazyload patches :-)

Code:
wget http://moodeaudio.org/test/lazyload-update.zip
unzip -q ./lazyload-update.zip
sudo mv ./playerlib.js /var/www/js
sudo mv ./scripts-panels.js /var/www/js
sudo rm ./lazyload*

-Tim
Reply
#23
The patch is rolled into moOde 5.3.1 update.
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#24
(06-15-2019, 07:43 PM)Ah.  I tried today after applying the update yesterday.  My performance problem is still there.  It takes a long time to load the initial screen when I first connect and response time is very slow, sometimes as much as 30 seconds.  I should keep more careful track, but, other than when first connecting, the lag seems random.  Sometimes when I tap on the screen (Android tablet) response time is sub second.  Other times it lags.  Beside the transition from one function to another I often have problems scrolling through lists.  This has been the case for me ever since moving to v 5.0  In v4 and previous releases response time was consistently quick.  A lesser problem is that the now playing screen does not always update.  If I\m reading or doing something else on the tablet when I switch back to Moode, the track shown on the screen is often several tracks behind the one actually playing.  I do have a large library although it seems like that shouldn Wrote: The patch is rolled into moOde 5.3.1 update.
Reply
#25
it will be difficult to troubleshoot based solely on a description of the symptoms. Try to provide more information for example:

- Errors or other indications in the logs (moode log, mod log, syslog)
- Try other clients (PC, Mac, etc)
- Try different SDCard
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#26
I can confirm that too - sometimes have to reload site to update.

The response time have helped a lot from 5.3 to 5.3.1 but we are not seeing 3.x niveau
yet  Wink
One strange thing - when in Album view and I do a search, then no cover images is
shown in result- just blank squares.

RPI 3 B+
Moode 5.3.1
iPad Pro 10.50"

All but LAN disabled
Reply
#27
I can repro.

Until I get time to investigate just tap the Album view button again and it will start the image lazy loader.

-Tim
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#28
Confirmed it's a bug.

Give this patch a try. You prolly have to refresh Browser multiple times b4 the updated JS gets loaded

Code:
wget -q http://moodeaudio.org/test/scripts-panels.js.zip
unzip -q scripts-panels.js.zip
sudo cp scripts-panels.js /var/www/js
rm -rf scripts-panels.js*

-Tim
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#29
It may be due to the tablet I'm using as a terminal, a Google Nexus 2013 running LineageOS Android 7 equivalent.  On a 3 year old ASUS tablet response times are better but not perfect, and on my desktop machine response time is acceptable.  The Google Nexus worked fine with Moode 4x.  Since the Nexus has had the standard broken USB port for several years I've been looking for an excuse to replace it.  Inductive charging is the only thing that's kept it alive. <g>




(06-15-2019, 09:06 PM)Tim Curtis Wrote: it will be difficult to troubleshoot based solely on a description of the symptoms. Try to provide more information for example:

- Errors or other indications in the logs (moode log, mod log, syslog)
- Try other clients (PC, Mac, etc)
- Try different SDCard
Reply
#30
(06-25-2019, 07:47 PM)Finally got the time to try a different SD card.  That solved the problem.   nosferatu_cat Wrote: It may be due to the tablet I'm using as a terminal, a Google Nexus 2013 running LineageOS Android 7 equivalent.  On a 3 year old ASUS tablet response times are better but not perfect, and on my desktop machine response time is acceptable.  The Google Nexus worked fine with Moode 4x.  Since the Nexus has had the standard broken USB port for several years I've been looking for an excuse to replace it.  Inductive charging is the only thing that's kept it alive. <g>




(06-15-2019, 09:06 PM)Tim Curtis Wrote: it will be difficult to troubleshoot based solely on a description of the symptoms. Try to provide more information for example:

- Errors or other indications in the logs (moode log, mod log, syslog)
- Try other clients (PC, Mac, etc)
- Try different SDCard
Reply


Forum Jump: