My music collection's about 3.5TB (>100000 tracks) and moode's fine with that, however I usually use a tablet to run the web interface and control moode, also recently used Roon with Moode as the endpoint and sometimes use the MALP mpd client.
I'm guessing when you say you have a touchscreen that you're running the local display option on the Pi and thus the Pi is also running a web browser to render the web interface. When the web browser is rendering long lists, like when you create a 15000 track playlist for example, the web browser has to generate and display a lot of html and thus can be quite demanding on something like a Pi3. Moode's web ui can be quite demanding in general if the library is large and the browser is running on underpowered hardware.
The Pi3 is easily powerful enough to manage a mpd library of this size and perform audio playback in mpd and the other bundled renderers but might be sluggish at running the web interface in a local browser with a long playlist like this, also if your Pi is locking up completely (ie you can't access it from the network) it might be running out of memory running Chromium locally. There's been discussions on this forum about the bundled Chromium browser recently exhausting the memory on some Pis and the possible workarounds such as changing out chromium for firefox.
For the best experience you might want to look at accessing Moode's web ui from a mobile device like a tablet or phone which should be quicker than a Pi also you don't have to get out of your seat to control moode then. Otherwise try to avoid going to the now playing sceen when a massive playlist is loaded.
I'm guessing when you say you have a touchscreen that you're running the local display option on the Pi and thus the Pi is also running a web browser to render the web interface. When the web browser is rendering long lists, like when you create a 15000 track playlist for example, the web browser has to generate and display a lot of html and thus can be quite demanding on something like a Pi3. Moode's web ui can be quite demanding in general if the library is large and the browser is running on underpowered hardware.
The Pi3 is easily powerful enough to manage a mpd library of this size and perform audio playback in mpd and the other bundled renderers but might be sluggish at running the web interface in a local browser with a long playlist like this, also if your Pi is locking up completely (ie you can't access it from the network) it might be running out of memory running Chromium locally. There's been discussions on this forum about the bundled Chromium browser recently exhausting the memory on some Pis and the possible workarounds such as changing out chromium for firefox.
For the best experience you might want to look at accessing Moode's web ui from a mobile device like a tablet or phone which should be quicker than a Pi also you don't have to get out of your seat to control moode then. Otherwise try to avoid going to the now playing sceen when a massive playlist is loaded.
