Say a new movie is on Netflix.  Or latest season of cards.  Everyone is going 
to want to watch it.  So 1000 simultaneous backbone streams to Netflix vs 1000 
simultaneous streams to the caching server in your NOC.  I choose the latter.


--------------------------------------------------------------------------------

From: "Ken Hohhof" <[email protected]>
To: [email protected]
Sent: Monday, March 23, 2015 11:08:27 AM
Subject: Re: [AFMUG] testing DNS server performance


I don’t understand how the caching server is going to help with CDNs.  
Actually, with so much Internet content now being either dynamic HTML or 
streaming, I wouldn’t think caching would be worth it, unless you are talking 
about something like a Netflix OpenConnect appliance.  Maybe you can cache 
software updates, I’m not sure about that.


From: That One Guy 
Sent: Monday, March 23, 2015 10:35 AM
To: [email protected] 
Subject: Re: [AFMUG] testing DNS server performance

Geographically close CDNs. I want to make sure we are getting content from 
Illinoisish rather than california for netflix, since all that matters is 
netflix

On Mon, Mar 23, 2015 at 10:30 AM, Josh Baird <[email protected]> wrote:

  For performance, look at queryperf which I think is provided by ISC/bind. 

  I'm not sure what you mean by "we are getting good CDNs and the like," though.

  Josh

  On Mon, Mar 23, 2015 at 11:27 AM, That One Guy <[email protected]> 
wrote:

    Im bringing live our first caching server today. Is there a good tool for 
comparing queries between DNS servers. 
    Im not all that concerned about speed since we are so small there wont be a 
huge amount of benefit I would think. Im primarily wanting to make sure we are 
getting good CDNs and the like


    -- 

    If you only see yourself as part of the team but you don't see your team as 
part of yourself you have already failed as part of the team.





-- 

If you only see yourself as part of the team but you don't see your team as 
part of yourself you have already failed as part of the team.

Reply via email to