Building Web Cache Cluster using LVS - Revision history

Wensong: /* Configuration Example */

2006-11-30T13:48:22Z

‎Configuration Example

Wensong at 15:46, 27 August 2006

2006-08-27T15:46:37Z

Wensong at 14:29, 22 January 2006

2006-01-22T14:29:01Z

Wensong at 13:45, 6 October 2005

2005-10-06T13:45:25Z

Wensong at 08:45, 20 August 2005

2005-08-20T08:45:39Z

Wensong: /* Architecture */

2005-07-14T15:35:19Z

‎Architecture

Wensong at 09:19, 3 July 2005

2005-07-03T09:19:00Z

Wensong at 02:03, 3 July 2005

2005-07-03T02:03:19Z

Wensong at 01:11, 3 July 2005

2005-07-03T01:11:33Z

New page

== Introduction ==

Efficient web cache systems can greatly reduce network traffic, lower the response time of web service and the loading of web servers.

== Architecture ==

[[Image:Cache-cluster.jpg|center]]

← Older revision		Revision as of 13:48, 30 November 2006
Line 24:		Line 24:
	== Configuration Example ==		== Configuration Example ==

		+	=== Web Cache Cluster ===
		+
		+	=== Transparent Proxy Cluster ===

	== Conclusion ==		== Conclusion ==

← Older revision		Revision as of 15:46, 27 August 2006
Line 26:		Line 26:

	== Conclusion ==		== Conclusion ==
		+
		+	== References ==
		+
		+	* [http://www.linuxvirtualserver.org/docs/PilotService.html Load Balancing The UK National JANET Web Cache Service Using Linux Virtual Servers]
		+	* [http://hermes.wwwcache.ja.net/ The National Janet Web Cache Service]

← Older revision		Revision as of 14:29, 22 January 2006
Line 27:		Line 27:
	== Conclusion ==		== Conclusion ==

		+
		+	{{lvs-example-stub}}

	[[Category:LVS Examples\|Cache]]		[[Category:LVS Examples\|Cache]]

@@ Line 13: / Line 13: @@
 [[Image:Cache-cluster.jpg|center]]
-* Load Balancer: it usually uses [[LVS/TUN]] or [[LVS/DR]] for high scalability
+* [[Load balancer|Load Balancer]]: it usually uses [[LVS/TUN]] or [[LVS/DR]] for high scalability
 * Cache Server Array: it performs web object caching services
-[[IPVS]] load balancer generally uses [[LVS/TUN]] method to build scalable cache cluster, when cache servers may be deployed at different places (for example, cache servers as proxy cache may be installed at the places near Internet backbone), load balancer and cache server array may not be in a physically network. When cache server array and [[IPVS]] load balancer are in one physical network, [[LVS/DR]] method is recommends for higher scalability.
+[[IPVS]] load balancer generally uses [[LVS/TUN]] method to build scalable cache cluster, when cache servers may be deployed at different places (for example, cache servers as proxy cache may be installed at the places near Internet backbone), [[load balancer]] and cache server array may not be in a physically network. When cache server array and [[IPVS]] load balancer are in one physical network, [[LVS/DR]] method is recommends for higher scalability.
 When [[LVS/TUN]] or [[LVS/DR]] is adopted, load balancer only dispatches requests, and cache servers return response data to clients directly. If request objects are not hit in local cache, cache server will get the objects from source directly. We can see that in this transaction, load balancer just dispatches one request, cache server sends request to source server and get response directly, then returns data to client directly. If [[LVS/NAT]] approach is used in proxy cache cluster, all these four flows have to go through load balancer, thus load balancer would be bottleneck. Therefore, [[LVS/TUN]] and [[LVS/DR]] methods are very effective for building scalable cache cluster.
@@ Line 28: / Line 28: @@
-[[Category:LVS Examples]]
+[[Category:LVS Examples|Cache]]

← Older revision		Revision as of 08:45, 20 August 2005
Line 26:		Line 26:

	== Conclusion ==		== Conclusion ==
		+
		+
		+	[[Category:LVS Examples]]

@@ Line 4: / Line 4: @@
 Single server system usually doesn't have good scalability. For example, if we want to build a web cache service that can handle several gigabit/sec traffic in ISP or backbone network, SUN Enterprise 10000 server cannot meet this throughput requirement. Thus, it's an efficient way to build scalable web service using clusters of commodity PC servers, it's also a way of highest performance/price ratio.
 == Architecture ==
 [[Image:Cache-cluster.jpg|center]]
 == Configuration Example ==

@@ Line 1: / Line 1: @@
 == Introduction ==
-Efficient web cache systems can greatly reduce network traffic, lower the response time of web service and the loading of web servers.
+Efficient web cache systems can greatly reduce network traffic, lower the response time of web service and the loading of web servers. However, if the cache server is overloaded so that it cannot process requests in time, it will increase the response time of service requests. Therefore, it's very important to have scalability in cache systems, when the load that the system receives is increasing, the whole system can be scaled up to have higher processing capacity of caching service.
 == Architecture ==
 [[Image:Cache-cluster.jpg|center]]