Load balancing - Revision history

Jk070707: /* Layer-2 Load Balancing */

2008-02-03T23:03:57Z

‎Layer-2 Load Balancing

Jk070707: /* Layer-2 Load Balancing */

2008-02-02T07:46:19Z

‎Layer-2 Load Balancing

Jk070707: /* Layer-2 Load Balancing */

2008-02-01T10:36:30Z

‎Layer-2 Load Balancing

Wensong: /* Layer-4 Load Balancing */

2007-04-29T14:58:09Z

‎Layer-4 Load Balancing

Wensong: /* Layer-7 Load Balancing */

2007-04-18T12:22:11Z

‎Layer-7 Load Balancing

Wensong at 14:36, 9 April 2007

2007-04-09T14:36:32Z

Wensong: /* Layer-7 Load Balancing */

2006-12-03T07:25:26Z

‎Layer-7 Load Balancing

Wensong: /* Layer-7 Load Balancing */

2006-11-12T01:39:17Z

‎Layer-7 Load Balancing

Wensong at 04:08, 27 May 2006

2006-05-27T04:08:12Z

Riyesh: /* Network Load Balancing */

2006-05-23T10:41:30Z

‎Network Load Balancing

@@ Line 13: / Line 13: @@
 === Layer-2 Load Balancing ===
-Layer-2 load balancing, aka link aggregation, etherchannel, or gigabit etherchannel port bundling is to bond two or more links into a single, higher-bandwidth logical link. Aggregated links also provide redundancy and fault tolerance if each of the aggregated links follows a different physical path. Link aggregation may be used to improve access to public networks by aggregating modem links or digital lines. Link aggregation may also be used in the enterprise network to build multigigabit backbone links between Gigabit Ethernet switches. See also NIC teaming or Link Aggregation Control Protocol(LACP)
+Layer-2 load balancing, aka link aggregation, port aggregation, etherchannel, or gigabit etherchannel port bundling is to bond two or more links into a single, higher-bandwidth logical link. Aggregated links also provide redundancy and fault tolerance if each of the aggregated links follows a different physical path. Link aggregation may be used to improve access to public networks by aggregating modem links or digital lines. Link aggregation may also be used in the enterprise network to build multigigabit backbone links between Gigabit Ethernet switches. See also NIC teaming or Link Aggregation Control Protocol(LACP)
 The Linux kernel has the Linux bonding driver, which can aggregate multiple links for higher throughput or fault tolerance.

@@ Line 13: / Line 13: @@
 === Layer-2 Load Balancing ===
-Layer-2 load balancing, aka link aggregation, etherchannel, or port trunking is to bond two or more links into a single, higher-bandwidth logical link. Aggregated links also provide redundancy and fault tolerance if each of the aggregated links follows a different physical path. Link aggregation may be used to improve access to public networks by aggregating modem links or digital lines. Link aggregation may also be used in the enterprise network to build multigigabit backbone links between Gigabit Ethernet switches. See also NIC teaming or Link Aggregation Control Protocol(LACP)
+Layer-2 load balancing, aka link aggregation, etherchannel, or gigabit etherchannel port bundling is to bond two or more links into a single, higher-bandwidth logical link. Aggregated links also provide redundancy and fault tolerance if each of the aggregated links follows a different physical path. Link aggregation may be used to improve access to public networks by aggregating modem links or digital lines. Link aggregation may also be used in the enterprise network to build multigigabit backbone links between Gigabit Ethernet switches. See also NIC teaming or Link Aggregation Control Protocol(LACP)
 The Linux kernel has the Linux bonding driver, which can aggregate multiple links for higher throughput or fault tolerance.

@@ Line 13: / Line 13: @@
 === Layer-2 Load Balancing ===
-Layer-2 load balancing, also known as link aggregation or trunking, is to bond two or more links into a single, higher-bandwidth logical link. Aggregated links also provide redundancy and fault tolerance if each of the aggregated links follows a different physical path. Link aggregation may be used to improve access to public networks by aggregating modem links or digital lines. Link aggregation may also be used in the enterprise network to build multigigabit backbone links between Gigabit Ethernet switches.
+Layer-2 load balancing, aka link aggregation, etherchannel, or port trunking is to bond two or more links into a single, higher-bandwidth logical link. Aggregated links also provide redundancy and fault tolerance if each of the aggregated links follows a different physical path. Link aggregation may be used to improve access to public networks by aggregating modem links or digital lines. Link aggregation may also be used in the enterprise network to build multigigabit backbone links between Gigabit Ethernet switches. See also NIC teaming or Link Aggregation Control Protocol(LACP)
 The Linux kernel has the Linux bonding driver, which can aggregate multiple links for higher throughput or fault tolerance.

@@ Line 19: / Line 19: @@
 === Layer-4 Load Balancing ===
-Layer-4 load balancing is to distribute requests to the servers at transport layer, such as TCP, UDP and SCTP transport protocol. The [[load balancer]] distributes network connections from clients who know a single IP address for a service, to a set of servers that actually perform the work. Since connection must be established between client and server in connection-oriented transport before sending the request content, the [[load balancer]] usually selects a server without looking at the content of the request.
+[[Layer-4 load balancing]] is to distribute requests to the servers at transport layer, such as TCP, UDP and SCTP transport protocol. The [[load balancer]] distributes network connections from clients who know a single IP address for a service, to a set of servers that actually perform the work. Since connection must be established between client and server in connection-oriented transport before sending the request content, the [[load balancer]] usually selects a server without looking at the content of the request.
 [[IPVS]] is an implementation of layer-4 load balancing for the Linux kernel, and has been ported to FreeBSD recently.

@@ Line 27: / Line 27: @@
 === Layer-7 Load Balancing ===
-Layer-7 load balancing, also known as application-level load balancing, is to parse requests in application layer and distribute requests to servers based on different types of request contents, so that it can provide quality of service requirements for different types of contents and improve overall cluster performance. The overhead of parsing requests in application layer is high, thus its scalability is limited, compared to layer-4 load balancing.
+[[Layer-7 load balancing]], also known as [[application-level load balancing]], is to parse requests in application layer and distribute requests to servers based on different types of request contents, so that it can provide quality of service requirements for different types of contents and improve overall cluster performance. The overhead of parsing requests in application layer is high, thus its scalability is limited, compared to layer-4 load balancing.
 [[KTCPVS]] is an implementation of layer-7 load balancing for the Linux kernel. With the appropriate modules, the Apache, Lighttpd and nginx web servers can also provide layer-7 load balancing as a reverse proxy.

← Older revision		Revision as of 14:36, 9 April 2007
Line 52:		Line 52:

	[[Database Load Balancing\|Database load balancing]] is to balance database access requests among cluster of database servers, in order to achieve database scalability and high availability.		[[Database Load Balancing\|Database load balancing]] is to balance database access requests among cluster of database servers, in order to achieve database scalability and high availability.
		+
		+	== SIP Load Balancing ==
		+
		+	[[SIP Load Balancing]] is to load balance SIP related services, in order to achieve performance scalability and high availability of the services.

	== Computing Load Balancing ==		== Computing Load Balancing ==

@@ Line 29: / Line 29: @@
 Layer-7 load balancing, also known as application-level load balancing, is to parse requests in application layer and distribute requests to servers based on different types of request contents, so that it can provide quality of service requirements for different types of contents and improve overall cluster performance. The overhead of parsing requests in application layer is high, thus its scalability is limited, compared to layer-4 load balancing.
-[[KTCPVS]] is an implementation of layer-7 load balancing for the Linux kernel. With the appropriate modules, the Apache and Lighttpd web servers can also provide layer-7 load balancing as a reverse proxy.
+[[KTCPVS]] is an implementation of layer-7 load balancing for the Linux kernel. With the appropriate modules, the Apache, Lighttpd and nginx web servers can also provide layer-7 load balancing as a reverse proxy.
 === MPLS Load Balancing ===

← Older revision		Revision as of 04:08, 27 May 2006
Line 56:		Line 56:

	Computing load balancing is to split a computational task across many different nodes in the cluster, so that the whole cluster system can provide increased performance. This kind of cluster systems is also known as [[High-performance cluster]], which is most commonly used in scientific computing.		Computing load balancing is to split a computational task across many different nodes in the cluster, so that the whole cluster system can provide increased performance. This kind of cluster systems is also known as [[High-performance cluster]], which is most commonly used in scientific computing.
		+
		+	[[Category:Terms and Abbreviations]]

@@ Line 35: / Line 35: @@
 MPLS load balancing is to balance network services based on the Multiprotocol Label Switching ([[MPLS]]) label information.
-See [[MPLS Load Balancing]] for more information.
+See [[MPLS Load Balancing]] for more information..
 == DNS Load Balancing ==