Network Spike when streaming from TwonkyServer

General discussion about the media server. Feature requests. Hints, tips and tricks.
Locked
johnnyleitrim
Posts:2
Joined:Mon Jul 25, 2011 9:35 am
AV Hardware:Windows 7 64bit, XBox 360
Network Spike when streaming from TwonkyServer

Post by johnnyleitrim » Mon Jul 25, 2011 9:42 am

Environment: TwonkyServer v6.0.34 on Windows 7 64bit streaming to XBox 360.

I was using TwonkyServer on Linux and everything was fine. For different reasons, I had to reinstall the machine with Windows 7 64bit. Now when I watch a movie on my XBox 360 from TwonkyServer, there are large network spikes about every 20 minutes (task manager on windows reports the wireless network goes to about 70% of 130Mbps for several seconds). After this spike, there is very little traffic until the next spike. When the spikes occur, the XBox freezes for about 3 seconds, and then continues to play. It almost seems like the XBox downloads large chunks of the file at a time rather than constantly streaming?? I did not see this behaviour when running Twonky on Linux.

Does anyone know why this might be happening, or what steps I could use to diagnose the issue?

User avatar
parnott
Posts:326
Joined:Mon Sep 20, 2010 9:55 pm
AV Hardware:Twonky, WDTV Live, XBMC (Linux & Windows)

Re: Network Spike when streaming from TwonkyServer

Post by parnott » Tue Jul 26, 2011 6:33 pm

Regular network traffic spikes at 20min intervals sounds more like the the Win Master Browser election process kicking in. Standard and required for Windows networking to function.

So why did you not see this with Linux? Only guess is that your Linux did not have Samba turned on.

johnnyleitrim
Posts:2
Joined:Mon Jul 25, 2011 9:35 am
AV Hardware:Windows 7 64bit, XBox 360

Re: Network Spike when streaming from TwonkyServer

Post by johnnyleitrim » Thu Jul 28, 2011 3:59 pm

Hi parnott,

Thanks for the reply. I'll take a look into that Win Master Browser stuff - but by what you say it sounds like Imay be stuck with it :(

No linux support for some new hardware I got (even though it said it was supported, the manufacturer released a v2 which wasn't :( ) hence moving to windows

Locked