I'm after advice re. an issue with a JRiver “client-server” set-up. We’re running a JRiver instance in our family room on a HTPC with a Digital TV Tuner, small SSD for OS (and media Library), large SSD for TV recordings and network connection to a Synology NAS for stored music and movies. A second JRiver instance is then located in our spare room with this being a bare bones set-up that leverages the media library from the HTPC. Our issue is with the “client” in the spare room which, when it’s first used after a period of inactivity, is painfully slow to navigate in Theatre View but once playback starts everything is fine. Any ideas as to the cause of the problem and/or potential solutions?
P.S. The link (
https://wiki.jriver.com/index.php/Troubleshooting_Network_and_Slow_Storage#Try_a_Different_Disk about the importance of the performance of the disk on which the library is maintained. Our set-up sees this stored on an internal SSD that also host the OS (Windows 10). What is the best practise – an internal SSD or spinning drive?
Author
Topic: Remote "Client" slow to react in Client-Server set-up (Read 1365 times)