Forum member “phil” has let us know that TwonkyMedia have resolved an issue with TwonkyMedia Server 5.1.2 that many of you have commented on in the forums concerning high CPU utilisation. TwonkyMedia suggest a patch was delivered to HP in December so we could expect that patch in “early March”.
Rick over at the TwonkyMedia Forums has posted:-
HP MediaSmart Server issues
by TMM_Product_Manager on Sun Jan 31, 2010 6:33 pmSome users here have reported problems with high CPU utilization and their HP MediaSmart servers . We believe that all TwonkyServer-related issues that may have contributed to high CPU usage have been fixed. Before December, we delivered an update to HP that contained several fixes (TMS 5.1.2). Unfortunately there is a delay between the time we turn updates to HP and the time they deploy them to the field. We’re trying to contact HP to get more information about when they plan to release this, but so far have not heard back from them.
Please note:
There may still be other “Media Collector” or Media Converter-related CPU issues that are outside of our control because we did not create those apps for HP.- Rick
And the update from HP.
TMM_Product_Manager
Good news. Just got an update from our contact at HP on this.
We’re aware of 2 problems with the current version of TwonkyMedia server that we are shipping. Both cause the CPU utilization to max out at 100%. In one case it occurs with system with a large media library when adding or removing new media – this usually dies down after the DB updates are complete. However, our support team has also received customer issues for brand new systems with no media at all. The CPU usage pegs at 100% and never dies down. We have been unable to reproduce this problem for defect tracking. We have been in contact with your team and they were not able to repro this problem either, but they did fix the first problem and provided us a drop for testing.
We are in the process of trying to get this fix to some of our customers with the second problem – to see if it fixes this issue as well. Right now we are waiting to hear back from our support team on this. If it proves to fix both problems, then we will be building the update package to distribute this fix in Feb; and will likely release in early March. If it does not fix the second problem, then we may need to try to work with your team to better isolate the problem and get a fix implemented. This would delay the release of the fix for the first problem as well.
I will provide more updates as I get them.
- Rick
I think this is great news, and do hope to see a fix soon as I’m one of those customers with the issue and have had to disable the twonky service to make my system usable. Maybe it will make it in the February 3.0 Update
{ 12 comments }
Thats great news for sure. Personally I would prefer they fix the issue in the 3.0 update for the older MSS’s before they start selling the update but thats my opinion and maybe in part thats one of the reasons why there is a delay even though it was not mentioned.
Twonky never worked properly on my ex485. Streaming media over the internet for family and friends was the only reason I bought the HP. I will never purchase another HP product. The misrepresentation of the capabilities of this product is disgraceful. I’m building a replacement system for the ex485 that will have the power and flexibility to meet my needs. I don’t mind spending time and effort to get a system to work when I build it myself, but when I buy a retail product I expect it to work as advertised. I wasted months of time and effort trying to get streaming media to work on the ex485. The end result was to conclude that the HP WHS products are fine for backup and file sharing. They should be embarrased to call them “Media Smart”, they just don’t have the horsepower for the job. Media collector still has issues.
Forget HP. Build a decent system for your own needs, you’ll be much happier.
I have the 3.0 upgrade running on my 470 with 2G of mem. I do not use the media features of my MediaSmart server. The TwonkyMediaServer.exe process hogs the CPU. Immediately after booting the server and for about 5 minutes, I cannot use the Home Server Console nor can I Remote Connect. The CPU is too busy to service the Console or the Remote Connection. Once I finally get the screen to paint on the Remote Connection, I launch the task manager and I have routinely seen TwonkyMediaServer.exe consuming 60 to 80% of the CPU!!!!
After every reboot I go into the Console and select Media/Media Server, it will show that sharing is enabled. It is not sticky across re-boots!!!!!!
Does anyone know how to lower the priority in a sticky way for the TwonkyMediaServer.exe process?
Does anyone know how to make the sharing/not-sharing state sticky across reboots?
Leif
Did this ever get resolved? My EX485 still ramps up to 100% anytime I turn Twonky gets turned on… and I have autoupdate setup. Help?
Rich, I’ve heard nothing new from HP on this but I do have the steps documented to resolve it on your own here.
http://www.mediasmartserver.net/2010/03/04/how-to-fix-twonky-issues-in-3-0-patch-2/
Thanks, Alex. I’ve done those steps before on finding the “bad file”… but then I rip some CD’s, buy some music online, rip another DVD, and i have another “bad file” that freezes Twonky. I certainly shouldn’t have to, but I think I’ll go the $20 license route… it’s irritating and it won’t be as integrated as the version HP provided… but it will work. Thanks again for all your help.
I’ve had patch 3 installed for some time now and it makes no difference to my EX-490 system. Twonkymedia server still has CPU running at 100% and it takes about 3-5 minutes to logon to the console.
It’s frustrating and had to be said, a tad annoying!
Well, took the radical step of removing the existing version of Twonkymedia server from my WHS and installing the latest version (6.01).
I used the Windows Desktop version, choosing to run as a service. The only difference that I can see is that it no longer shows up in the WHS console under settings but that’s no great loss. I installed it through RDP and used an existing server licence key I already had. Not sure if it’s possible to extract the key from the original version installed on WHS?
Anyway, the results are staggering. 5-10% Max load on CPU at all times.
It works a treat and all I had to do was specify the path to the WHS shares for my music, photos and videos.
Well sorted. Thanks for nothing HP!
Drew, Did you RDP in to remove the HP provided version on Twonky? What prompted you to choose the desktop version to run on your WHS instead of the WHS version? I’m ready to spend the $20 just to get it to WORK… but curious why you chose that version.
You guys do realize you can just turn off Twonky and use the built-in Windows Media Connect service for basic streaming in the house?
Agreed Alex however, I used Twonky well before I ventured down the WHS route and wanted to stick to using this.
Hi Rich,
I downloaded the latest release of mediaserver for WHS and according to their support FAQ, that was the recommended installation for using this version with WHS
http://www.twonkyvision.de/upfiles/Install%20TwonkyServer%20on%20Windows%20HomeServer-EN.pdf
The Twonky site is misleading in that it’s the same version for Windows XP/7 and WHS which is why I mentioned desktop version. It could be that theyhave rolled it all into the one product.
Yes uninstalled through RDP.
{ 5 trackbacks }