This message board is post-moderated
This discussion has been closed.
Of course it's all Kontiki's fault; these are common problems with Sky and 4OD, and yet the BBC sees fit to use the same P2P component?
When I attempt to download a single short program it's fine, probably because there aren't many requests for it. When I choose something popular; like say Top Gear, you can kiss your CPU goodbye. I must admit it's impressive to see a single windows server take 99% of the CPU on a 2Ghz Pentium; I can't even get SQL Server to do that when I'm doing massive queries.
And of course to top it all off there's no way to limit the bandwidth used by Kontiki at all; inbound or outbound; not that you can type when the CPU is pegging that high.
So not impressed. Uninstalled after I had to kill the Kontiki process (of course after a reboot it starts) and then the Kontiki uninstall.
Editorial Note: This conversation has been moved from 'Known bugs and issues' to 'General Discussion'.
This is a reply to this message.
Copyright © 2015 BBC. The BBC is not responsible for the content of external sites. Read more.
This page is best viewed in an up-to-date web browser with style sheets (CSS) enabled. While you will be able to view the content of this page in your current browser, you will not be able to get the full visual experience. Please consider upgrading your browser software or enabling style sheets (CSS) if you are able to do so.