|
On March 09 2011 13:00 Sea.3PO wrote:What does a DNS server have to do with speed tests?
A fast dns server speeds up your browsing by quickly resolving dns lookups sometimes much faster than your isp can. So basically your pages load faster. Here's a tool you can test against to see the difference.
http://code.google.com/p/namebench/
|
Tracing route to justin.tv [199.9.249.19] over a maximum of 30 hops:
1 10 ms 8 ms 6 ms c-69-245-72-1.hsd1.mi.comcast.net [69.245.72.1]
2 13 ms 12 ms 12 ms ge-2-2-ur03.waterford.mi.michigan.comcast.net [6 8.85.218.69] 3 7 ms 10 ms 11 ms te-8-1-ur02.springfield.mi.michigan.comcast.net [68.87.190.122] 4 15 ms 9 ms 9 ms te-0-5-0-6-ar01.pontiac.mi.michigan.comcast.net [68.87.190.126] 5 36 ms 23 ms 22 ms pos-3-3-0-0-cr01.chicago.il.ibone.comcast.net [6 8.86.90.109] 6 23 ms 22 ms 25 ms pos-1-3-0-0-pe01.350ecermak.il.ibone.comcast.net [68.86.86.158] 7 22 ms 24 ms 23 ms te0-3-0-1.ccr22.ord03.atlas.cogentco.com [154.54 .10.253] 8 22 ms 25 ms 22 ms te0-3-0-0.ccr22.ord01.atlas.cogentco.com [154.54 .5.1] 9 33 ms 35 ms 35 ms te0-1-0-1.ccr22.dca01.atlas.cogentco.com [154.54 .40.205] 10 34 ms 33 ms 35 ms te0-2-0-0.mpd21.dca01.atlas.cogentco.com [154.54 .7.233] 11 41 ms 33 ms 34 ms te0-3-0-5.mpd21.iad02.atlas.cogentco.com [154.54 .41.246] 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out.
anything out of the ordinary?
|
It's because you didn't whitelist Teamliquid.net.
But I have been fine until todays GCPL stream, but that may have been because there were like 8000 people watching.
|
Yeah i always seem to have a real problem with it on my school internet no matter the quality even though we have 101 mb/s up and 50 mb/s down, but when i am home or at a friends it always seems to work fine even with a much slower connection.
|
On March 12 2011 20:14 Baarn wrote:Show nested quote +On March 09 2011 13:00 Sea.3PO wrote:On March 09 2011 11:51 Baarn wrote:What dns servers are you using? If it is auto or isp I'd recommend changing to 4.2.2.1, 4.2.2.2 which are level 3 dns servers. I use them and here are recent results. http://www.speedtest.net/result/1191586810.png What does a DNS server have to do with speed tests? A fast dns server speeds up your browsing by quickly resolving dns lookups sometimes much faster than your isp can. So basically your pages load faster. Here's a tool you can test against to see the difference. http://code.google.com/p/namebench/
Your description is very correct, but DNS has nothing to do with sustained download speeds (which is required to watch a stream). A slow DNS lookup can cause a initial delay, but once the connection has been made, the DNS is no longer used. DNS simply cannot be the culprit when it comes to stream lag. To back up my statement
|
On March 14 2011 08:08 HellGreen wrote:Show nested quote +On March 12 2011 20:14 Baarn wrote:On March 09 2011 13:00 Sea.3PO wrote:On March 09 2011 11:51 Baarn wrote:What dns servers are you using? If it is auto or isp I'd recommend changing to 4.2.2.1, 4.2.2.2 which are level 3 dns servers. I use them and here are recent results. http://www.speedtest.net/result/1191586810.png What does a DNS server have to do with speed tests? A fast dns server speeds up your browsing by quickly resolving dns lookups sometimes much faster than your isp can. So basically your pages load faster. Here's a tool you can test against to see the difference. http://code.google.com/p/namebench/ Your description is very correct, but DNS has nothing to do with sustained download speeds (which is required to watch a stream). A slow DNS lookup can cause a initial delay, but once the connection has been made, the DNS is no longer used. DNS simply cannot be the culprit when it comes to stream lag. To back up my statement 
Really now? The information in the link you provided is incorrect as to how, let's say, googledns works. I'll give a real example with using Netflix as an example of how the dns actually does matter. Let's say you live on the east coast and are currently using a dns on the west coast. So when you connect to netflix you get a cdn that is obviously gonna be on the west coast when you connect. So your throughput isn't gonna be the same as if you switched to googledns and got a cdn on the east coast to connect to. Does that make sense to you now about how streaming services work on the web?
Another example is that Blizzard uses a local dns here in san diego for bnet servers where I live so that data center is a few miles from me. So by using a local dns here I can cut the time of my connection to their servers since the distance is so short meaning I will have a lower ping which helps a great deal in gaming.
|
I have the exact same problem as of the last few days. I've double checked all my hardware and every PC in the house, monitored all my bandwidth and what do you know...only justin.tv lags for me. WTF!
|
@Baarn It seems you're assuming there are multiple end points to each service. I'm not. I think we need to agree on what we're discussing. . I live in Denmark (Europe) and no matter what DNS I use a always get the same end point when watching a stream on www.justin.tv. This is because their servers are located in Berkeley, CA (ie. http://whatismyipaddress.com/ip/199.9.249.184). Now I agree that if a streaming service had multiple locations, you would probably get higher speeds from closest geo-location, but it shouldn't matter much from a througput point of view. Right now I'm watching a stream from the user "vVvrigid". I'm downloading ~1mbit/s. Whether I got connected to an East coast or West coast server really shouldn't be noticeable in throughput at those kind of speeds. There's a whole other discussion in this, from the providers POV that could affect the stream experience (even distribution of users and such), but that's not what we're discussing.
On March 14 2011 14:06 Baarn wrote: Let's say you live on the east coast and are currently using a dns on the west coast. So when you connect to netflix you get a cdn that is obviously gonna be on the west coast when you connect.
I'm sorry, but you're wrong in the assumption that only a physical close DNS server will give you the closest available service. Look up "Anycast" on Wikipedia. If set up correctly, you will get the closer server no matter which DNS you query.
On March 14 2011 14:06 Baarn wrote: So your throughput isn't gonna be the same as if you switched to googledns and got a cdn on the east coast to connect to. Does that make sense to you now about how streaming services work on the web?
In the context of this thread (about Justin.tv) who as far as I can tell, only have servers in California (Berkeley/San Francisco), it doesn't matter which DNS you query - they will all direct you to the same end point.
On March 14 2011 14:06 Baarn wrote: Another example is that Blizzard uses a local dns here in san diego for bnet servers where I live so that data center is a few miles from me. So by using a local dns here I can cut the time of my connection to their servers since the distance is so short meaning I will have a lower ping which helps a great deal in gaming. Whoa! This discussion was about DNS vs. sustained download speeds (throughput). Not ping times. I'm not arguing that using certain DNS services can improve your browsing speeds, I'm arguing that throughput against a single specific server is non-DNS related.
Best Regards,
|
As a side note to this discussion, last 2 days i have noticed not great but HUGE IMMENSE increase of performance when watching justin.tv. Before 240P lagged, now I have little trouble watching everything at best.
|
the dns server isn't the problem, i've tried multiple and have the same issue
can anyone who also is having this issue post in my justin.tv forum thread - http://community.justin.tv/forums/showthread.php?t=7495
i haven't gotten any responses from a moderator yet, so i'm hoping that if i get enough posts they wont be able to just brush this off and ignore it
after giving so much information documenting this problem it would be a shame if justin.tv never actually looked at it
|
i'm trying to watch the day9 daily and the stream is frozen 95% of the time even on 240p. there is no explanation. my internet is fine. i can watch 3 ustream channels at once with no problem.
|
jtv is such shit recently
|
can't watch idra's stream either. and everyone just recently switched to JTV
the canadian JTV servers are completely useless.
|
On March 15 2011 02:47 HellGreen wrote:@Baarn It seems you're assuming there are multiple end points to each service. I'm not. I think we need to agree on what we're discussing.  . I live in Denmark (Europe) and no matter what DNS I use a always get the same end point when watching a stream on www.justin.tv. This is because their servers are located in Berkeley, CA (ie. http://whatismyipaddress.com/ip/199.9.249.184). Now I agree that if a streaming service had multiple locations, you would probably get higher speeds from closest geo-location, but it shouldn't matter much from a througput point of view. Right now I'm watching a stream from the user "vVvrigid". I'm downloading ~1mbit/s. Whether I got connected to an East coast or West coast server really shouldn't be noticeable in throughput at those kind of speeds. There's a whole other discussion in this, from the providers POV that could affect the stream experience (even distribution of users and such), but that's not what we're discussing. Show nested quote +On March 14 2011 14:06 Baarn wrote: Let's say you live on the east coast and are currently using a dns on the west coast. So when you connect to netflix you get a cdn that is obviously gonna be on the west coast when you connect.
I'm sorry, but you're wrong in the assumption that only a physical close DNS server will give you the closest available service. Look up "Anycast" on Wikipedia. If set up correctly, you will get the closer server no matter which DNS you query. Show nested quote +On March 14 2011 14:06 Baarn wrote: So your throughput isn't gonna be the same as if you switched to googledns and got a cdn on the east coast to connect to. Does that make sense to you now about how streaming services work on the web?
In the context of this thread (about Justin.tv) who as far as I can tell, only have servers in California (Berkeley/San Francisco), it doesn't matter which DNS you query - they will all direct you to the same end point. Show nested quote +On March 14 2011 14:06 Baarn wrote: Another example is that Blizzard uses a local dns here in san diego for bnet servers where I live so that data center is a few miles from me. So by using a local dns here I can cut the time of my connection to their servers since the distance is so short meaning I will have a lower ping which helps a great deal in gaming. Whoa! This discussion was about DNS vs. sustained download speeds (throughput). Not ping times. I'm not arguing that using certain DNS services can improve your browsing speeds, I'm arguing that throughput against a single specific server is non-DNS related. Best Regards,
Justin.tv had multiple endpoints up until they decided to go on their own and drop amazon and akamai recently. I was under the impression, before reading an article or two, that they were still with those 2 companies which provide end points globally. Maybe once Justin is finished with their transition to their solo venture then things will improve? So in this situation I'll agree with you that dns isn't gonna help with connectivity to a cdn that only has 2 ip's currently in the same data center.
|
On March 09 2011 11:07 R1CH wrote: Are you getting packet loss? What's your OS? Have you tweaked your TCP settings? Any proxy / firewall software? Why do you hate the TL horse mascot?
LOL, Ad-block is on for him! xD I love how you actually caught that while none of the others did! xD What do you think would be better to stream? Chrome, FF or IE?
|
LOL, Ad-block is on for him! xD I love how you actually caught that while none of the others did! xD What do you think would be better to stream? Chrome, FF or IE?
different browsers shouldn't make any difference in viewing streams, they all use flash to load the player anyway
|
Hey I have this exact problem and only for justintv. I have done the pingtest and actually get an A rating at some times so I know it cant be my internet connection. Then additionally Ustream, youtube, gomtv all work perfectly fine with no delay. For some reason justintv will play for 5-10 sec then stop for ~2-3 sec then rpt. Super annoying and has made Day9 dailys pretty much unwatchable which is a shame cause live is so much better
Any suggestions on what I can do to fix it or is it all on justintv's end?
|
i was just forced to watch the justin.tv invitational - Lag
![[image loading]](http://img232.imageshack.us/img232/4189/justintvinvitationaljus.jpg) on own3d.tv - No Lag
![[image loading]](http://img850.imageshack.us/img850/6649/justintvinvitationalown.jpg)
and to add insult to injury, on my justin.tv forum account that i posted this thread with, all of my posts are required to be reviewed by a moderator before they are posted
i made a new justin.tv forum account, and the new account doesn't require moderator review
seriously?
|
On March 20 2011 06:57 BeanerBurrito wrote:i was just forced to watch the justin.tv invitational - Lag
slow down there buddy, nobody forced you to watch that
On March 20 2011 06:57 BeanerBurrito wrote:and to add insult to injury, on my justin.tv forum account that i posted this thread with, all of my posts are required to be reviewed by a moderator before they are posted
i made a new justin.tv forum account, and the new account doesn't require moderator review
seriously?
well that is just an ass move by justin.tv unless you were flaming them, then that's an understandable action.
I also always feel lag spikes only on justin.tv and no other streaming site.
What annoys me most is not that justin.tv lags but that they got casters to switch by promosing that they will fix the european lag issues in the near future. Which they did remedy to some degree, but if I can't watch a 240p on justin.tv but be fine watching a 720p stream from own3d then that is just not anywhere near "fixed"-status.
|
i wanted to watch the justin.tv invitational and because of horrible lag i was unable to watch it on any justin.tv stream, and therefore had to use an own3d.tv stream to be able to watch video, instead of a slideshow
the post on their forum is linked in the op, check it out and see if you think i was flaming lol
|
|
|
|