<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.iis.net/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:cs="http://blogs.iis.net/"><channel><title>Search results matching tags 'Media' and 'Hosting'</title><link>http://blogs.iis.net/search/SearchResults.aspx?o=DateDescending&amp;tag=Media,Hosting&amp;orTags=0</link><description>Search results matching tags 'Media' and 'Hosting'</description><dc:language>en-US</dc:language><generator>CommunityServer 2007 SP1 (Build: 20510.895)</generator><item><title>Customizing Bandwidth Usage</title><link>http://blogs.iis.net/media/archive/2007/08/02/customizing-bandwidth-usage.aspx</link><pubDate>Fri, 03 Aug 2007 00:27:00 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:1838872</guid><dc:creator>brflem</dc:creator><cs:applicationKey>media</cs:applicationKey><description>&lt;P mce_keep="true"&gt;First of all, apologies for not having introduced myself in my first post.&amp;nbsp; My name is Bryan and I am a Program Manager Intern on the IIS team.&amp;nbsp; In my "real life," I am an undergraduate student pursuing a double major in Electrical and Computer Engineering and Computer Science.&amp;nbsp; I have been at Microsoft since mid-May 2007.&lt;/P&gt;
&lt;P&gt;I have already &lt;A class="" title=posted href="http://blogs.iis.net/media/archive/2007/07/13/welcome-to-the-iis-media-blog.aspx" mce_href="http://blogs.iis.net/media/archive/2007/07/13/welcome-to-the-iis-media-blog.aspx"&gt;posted&lt;/A&gt; about delivering on-demand media more efficiently, because users often do not watch entire videos. &amp;nbsp;Download throttling for media is one of the things we are currently working on for our upcoming Media Pack.&lt;/P&gt;
&lt;P&gt;There is also another way to limit bandwidth use in IIS.&amp;nbsp; IIS6 and IIS7 allow an administrator to set a limit on the total bandwidth that can be used at the site and server levels.&amp;nbsp; This existing functionality has some interesting applications, but it is not a very good solution to the media problem. &lt;/P&gt;
&lt;P&gt;Where the existing bandwidth throttling might make sense is in a shared hosting scenario.&amp;nbsp; To ensure no one site incurs heavy traffic that could use all of a server's bandwidth, you could set a bandwidth limit of 80% of that server's total bandwidth for each site on the box.&amp;nbsp; That way no single site could ever be allowed to use enough bandwidth to completely choke out others.&lt;/P&gt;
&lt;P&gt;Setting a bandwidth limit can also potentially lower bandwidth cost, if the bill is somehow based on the peak or "average peak" bandwidth used.&amp;nbsp; Throttling allows an administrator to ensure that the bandwidth used never exceeds a set maximum, which can also mean that the bill will not exceed a set maximum.&amp;nbsp; Setting a limit to control cost can be especially beneficial for a server that routinely sends large files to clients with very fast connections, generating very high bandwidth usage for extended periods of time.&lt;/P&gt;
&lt;P&gt;Many folks are surprised to learn about the existing bandwidth limit feature, and I wanted to put it out into the community a little louder.&amp;nbsp; In the IIS Manager, select a site or server, and then click on "Limits..." under "Configure" in the Actions panel.&lt;/P&gt;</description></item></channel></rss>