Having upgraded from TMS 4.4.2 to TMS 5.1.2 I noticed that it took quite a while until all of my songs became visible. Under TMS 4.4.2 or earlier versions I never noticed such a long delay (my first TMS was from 2006).
To investigate I measured the speed of 11500 MP3 files to become available after restart of TMS. All MP3 files are with ID3 tags, only following fields are set: Track, Artist, Title, Album, Genre, Year
Both test measured a "re-start" of TMS with a previously build database (and no change in the MP3 files): I just started TMS an waited until all songs are counted in the status page:
With Twonky Media Server 4.4.2 it took 2min 37s: about 73 files per second
With Twonky Media Server 5.1.2 it took 31min 46s: about 6 files per second
While both tests were running I did not notice any paging on the Linux based device.
Can anybody confirm similar results and/or explain this regression?
I am a little bit disappointed about the TMS 5.1.2 result as am not patient enough to wait about half an hour after each restart (power up or configuration change) of the server.
Is there a way to speed up?
How to speed up startingTwonky Media Server 5.1.2?
-
ksmueller
- Posts:8
- Joined:Mon Jan 25, 2010 1:47 pm
- AV Hardware:UPnP servers: Twonky Media Server on NAS
UPnP client: Terratec Noxon 2 Audio
TwonkyMedia 7.2.70.0 on QNAP TS-112
Renderer Terratec Noxon 2 audio
Renderer Terratec Noxon 2 audio
-
Briain
- Posts:478
- Joined:Thu Jan 03, 2008 8:07 pm
- AV Hardware:Linn Klimax DS
Linn Majik DS-I
Linn Sneaky DS
WDTV Live Hib
Sonos 80 - Location:Edinburgh, Scotland
Re: How to speed up startingTwonky Media Server 5.1.2?
Hi
With rescan set to -1, Twonky 5.0 used to rescan the content directories when you restarted it (this took about 18 minutes with my collection). With rescan set to 0, Twonky 5.0 just started and worked. I'm testing 5.1.2 on a ReadyNAS (Linux sparc version) and irrespective of rescan settings, it looks like it is totally rebuilding the database whenever I restart Twonky (and obviously also when I reboot my NAS). With 19,000 FLAC files, this process takes about 30 minutes (I can't be exact as I'm testing a custom music tree and that has a massive impact on the rebuild times). I suspect it's maybe a bug in 5.1.2 (as opposed to something caused by me breaking Twonky) and I have made PV aware of it. In my case, I've done other things (like removing transcoding files as part of another experiment I'm working on) so this could be something that I've caused; however, I don't think it is and thus think it might be a genuine bug.
From what you describe in your post, it sounds like it might be doing the same. The way to see this is to restart Twonky then look at the server stats on the web interface. When I do that on mine, it starts of at 0 tracks and starts building them up.
I don't know if it's specific to my particular build, specific to all the Linux variants or whether it's not platform specific and thus impacts on all variants including the Windows versions. My guess (and hope) is that it might be addressed in the next release of 5.1.3 (RC2) or if not, hopefully by the time the final release is made available.
Bri
With rescan set to -1, Twonky 5.0 used to rescan the content directories when you restarted it (this took about 18 minutes with my collection). With rescan set to 0, Twonky 5.0 just started and worked. I'm testing 5.1.2 on a ReadyNAS (Linux sparc version) and irrespective of rescan settings, it looks like it is totally rebuilding the database whenever I restart Twonky (and obviously also when I reboot my NAS). With 19,000 FLAC files, this process takes about 30 minutes (I can't be exact as I'm testing a custom music tree and that has a massive impact on the rebuild times). I suspect it's maybe a bug in 5.1.2 (as opposed to something caused by me breaking Twonky) and I have made PV aware of it. In my case, I've done other things (like removing transcoding files as part of another experiment I'm working on) so this could be something that I've caused; however, I don't think it is and thus think it might be a genuine bug.
From what you describe in your post, it sounds like it might be doing the same. The way to see this is to restart Twonky then look at the server stats on the web interface. When I do that on mine, it starts of at 0 tracks and starts building them up.
I don't know if it's specific to my particular build, specific to all the Linux variants or whether it's not platform specific and thus impacts on all variants including the Windows versions. My guess (and hope) is that it might be addressed in the next release of 5.1.3 (RC2) or if not, hopefully by the time the final release is made available.
Bri