04-18-2019, 05:50 PM
(This post was last modified: 04-18-2019, 05:55 PM by Tim Curtis.
Edit Reason: eta
)
(04-18-2019, 05:33 PM)philrandal Wrote:(04-18-2019, 07:37 AM)sebastien Wrote:(04-18-2019, 06:09 AM)amontag52 Wrote: switched from 4.4 to 5.0 on an old Raspberry A: now connecting to moode.local is very very slow, many times I get impossible to connect.Therefore I cannot manage it remotely. Any comment?? is old Raspberry able to run 5.0?
Running on ethernet cable, and no issues with 4.4, that is curently playing radio stations
Hi,
Same issue here: UI is very slow on my PC to remotely manage a Raspberry Pi 3B.
I use Chrome browser running with Windows 7.
Configuring Moode took me a long time but now everything is in place and I use BubbleUPNP to control the player.
Initial slowness may be caused by mpd doing its thing scanning your music libraries.
That said, even after that, the UI seems glacially slow when loading config pages.
I'm going to put Moode on a Transcend high endurance SD card and see if that makes a difference.
99% of time due to factors external to moOde software for example poor network performance, bad sd card, user OS modifications and tweaking, metal enclosures attenuating wifi, client bottlenecks etc etc.
No issues with performance on my end with 6 Pi's: 3 on 5GHz wifi 2 on 2.4Ghz wifi and one on Ethernet. I normally gauge performance by stressing my lowest end Pi-ZeroW.
Generally to troubleshoot performance issues its necessary to isolate the bottleneck. Utilities like ping, top and free can sometimes reveal network, cpu or ram bottlenecks. There is probably a similar util for disk I-O but I've never had disk I-O issues on the SDCards I use.