https://wiki.kram.nz/index.php?action=history&feed=atom&title=SE401%3AGroup33%3AResearch%3AMark%3ATTL_Load_Balancing 2026-05-02T12:57:52Z Revision history for this page on the wiki MediaWiki 1.45.3 https://wiki.kram.nz/index.php?title=SE401:Group33:Research:Mark:TTL_Load_Balancing&diff=11121&oldid=prev 2008-11-03T05:21:47Z

<p>4 revision(s)</p> <p><b>New page</b></p><div>Load balancing for us can be done at the DNS level. This should be fairly easy with a static site. Probably use a simple round robin (even better RR2) technique.<br /> <br /> This paper<br /> *They explore using the TTL (Time To Live incase ya didn kno) values by &quot;adaptively setting the TTL value based on the client request rate and/or the server capacity can dramatically reduce system imbalance even in a highly heterogeneous distributed Web system&quot;<br /> *Round Robin isnt good enough so a two-tiered round robin (RR2) is &quot;found to provide the most robust peformance&quot;. The busy local gateways speak up and are moved to a separate round robin with different request rates.<br /> <br /> *Their adaptive TTL; small servers get a few big requests and powerful servers get a lot of small requests. This is combined with RR2<br /> <br /> *RR &amp; RR2 balance load among homogeneous distributed servers. &#039;&#039;probabilistic&#039;&#039; routing features may be added to extend this to heterogeteous distributions.<br /> <br /> *They modify the TTL values based on the additional component of server capacity.<br /> <br /> <br /> Performance<br /> <br /> * They list the assumptions they make for a performance test</div>

Mark