Performance metrics - Revision history

Abrassard: /* Available limits */

2018-06-22T16:19:04Z

Available limits

Allyntree: /* References */

2018-03-28T18:11:49Z

References

Cboulanger: Added "TMG7800" for reference to forum page on performance

2014-07-25T13:57:46Z

Added "TMG7800" for reference to forum page on performance

Abrassard: /* Available limits */

2013-03-15T11:11:26Z

Available limits

Candy Chan: /* Performance results */

2011-08-30T04:44:14Z

Performance results

Candy Chan: /* ISDN-SIP */

2011-08-30T04:43:59Z

ISDN-SIP

Cbilodeau at 19:30, 16 June 2011

2011-06-16T19:30:28Z

Cbilodeau: remove under construction

2011-06-16T19:16:59Z

remove under construction

Abrassard at 18:43, 16 June 2011

2011-06-16T18:43:40Z

Ktrueman: added link to article on forums

2009-12-15T14:50:06Z

added link to article on forums

@@ Line 74: / Line 74: @@
 The Toolpack system can regulate call rate:
 * Per [[NAP]]
-** Maximum call legs per second
+** Maximum call legs per second (incoming, outgoing or total)
 ** Maximum simultaneous incoming, outgoing and/or total calls
 ** Maximum processing delay

← Older revision		Revision as of 18:11, 28 March 2018
Line 108:		Line 108:
	== References ==		== References ==
	*[https://forums.telcobridges.com/viewtopic.php?f=13&t=123&p=505#p505 TMG7800 Toolpack performance tests] (registration required)		*[https://forums.telcobridges.com/viewtopic.php?f=13&t=123&p=505#p505 TMG7800 Toolpack performance tests] (registration required)
−
−
−	~~[[category:Needs revising]]~~

@@ Line 107: / Line 107: @@
 == References ==
-*[https://forums.telcobridges.com/viewtopic.php?f=13&t=123&p=505#p505 Toolpack performance tests] (registration required)
+*[https://forums.telcobridges.com/viewtopic.php?f=13&t=123&p=505#p505 TMG7800 Toolpack performance tests] (registration required)
 [[category:Needs revising]]

@@ Line 76: / Line 76: @@
 ** Maximum call legs per second
 ** Maximum simultaneous incoming, outgoing and/or total calls
 * Per TMedia unit
 ** Maximum call legs per second (per protocol type or total)
@@ Line 87: / Line 89: @@
 [[Image:Hardware_Call_Rate_Limit.png|widthpx| ]]
 === Algorithm used ===

← Older revision		Revision as of 04:44, 30 August 2011
Line 69:		Line 69:
	*Signaling protocol use, SIP takes a little longer to process, longer than ISDN or SS7.		*Signaling protocol use, SIP takes a little longer to process, longer than ISDN or SS7.

−
−	~~==Performance results ==~~

	==Limiting the call rate ==		==Limiting the call rate ==

← Older revision		Revision as of 04:43, 30 August 2011
Line 71:		Line 71:

	==Performance results ==		==Performance results ==
−
−	~~=== ISDN-SIP ===~~
−	~~Results expressed in bridged calls per second (BCPS)~~
−
−	*[[TMG800]]: 20 BCPS
−	*[[TMG3200]]: 20 BCPS
−	*[[TMG5800]]: 70 BCPS
−	*[[TMG7800]]: 670 BCPS
−

	==Limiting the call rate ==		==Limiting the call rate ==

@@ Line 90: / Line 90: @@
 ** Maximum call legs per second (per protocol type or total)
-Limiting the call rate can be configure through [[Web Portal]].
+Limiting the call rate can be configure through [[Web Portal]] (Warning: this feature is available for 2-5-94 or later).
-*For the [[NAP]], go to the [[Nap menu configuration]] page.
+*For the [[NAP]], go to the Nap menu page.
-*For the Tmedia unit, go to the [[Hardware menu configuration]] page.
 === Algorithm used ===

@@ Line 1: / Line 1: @@
 Performance is a popular and key component of the decision to adopt a particular brand or model of media gateway. While popular, the notion of performance for the purposes of comparison is often hard to nail down. This is due to both the underlying details of the hardware being compared as well as the applications and production environments that are unique to each service provider. There is not even a commonly accepted, universal, 'metric' for comparing performance across systems. The most frequently heard one, 'calls per second' can actually refer to many things. For our purposes, we will focus on bridged calls per second (BCPS).
@@ Line 85: / Line 83: @@
 ==Limiting the call rate ==
 === Available limits ===
-The Toolpack system (toolpack_engine application) allows to throttle the call rate:
+The Toolpack system can regulate call rate:
-* Per NAP
+* Per [[NAP]]
 ** Maximum call legs per second
 ** Maximum simultaneous incoming, outgoing and/or total calls
 * Per TMedia unit
 ** Maximum call legs per second (per protocol type or total)
-You will find appropriate configuration parameters in the Web Portal configuration pages under 'NAP' and 'Hardware' sections.
 === Algorithm used ===
@@ Line 103: / Line 104: @@
 === Typical usage ===
-Call rate limiting is generally used to avoid overloading a system's CPU (local TMedia unit or remote system) by sending too many calls per second.
+Call rate limiting is generally used to avoid overloading a system's CPU (local system or remote systems).
 Local system is generally protected using a per-adapter limit.
-Remote system is generally protected using a per-NAP limit.
+Remote systems are generally protected using a per-[[NAP]] limit.
-Maximum simultaneous calls limit is generally used to protect a NAP from being overloaded. It's frequently used for SIP NAPs to avoid RTP bandwidth to exceeds the capacity of the IP network. It's less frequently used for ISDN, CAS or SS7 as the number of CICs in the NAP already provides a limit to the number of simultaneous calls.
+Maximum simultaneous calls limit is generally used to protect a [[NAP]] from being overloaded. It's frequently used for SIP NAPs to avoid RTP bandwidth to exceeds the capacity of the IP network. It's less frequently used for [[ISDN]], [[CAS]] or [[SS7]] as the number of CICs in the [[NAP]] already provides a limit to the number of simultaneous calls.
 == References ==

← Older revision		Revision as of 18:43, 16 June 2011
Line 82:		Line 82:
	*[[TMG7800]]: 670 BCPS		*[[TMG7800]]: 670 BCPS

		+
		+	==Limiting the call rate ==
		+	=== Available limits ===
		+	The Toolpack system (toolpack_engine application) allows to throttle the call rate:
		+	* Per NAP
		+	** Maximum call legs per second
		+	** Maximum simultaneous incoming, outgoing and/or total calls
		+	* Per TMedia unit
		+	** Maximum call legs per second (per protocol type or total)
		+	You will find appropriate configuration parameters in the Web Portal configuration pages under 'NAP' and 'Hardware' sections.
		+
		+	=== Algorithm used ===
		+	The algorithm to limit the call rate is based on the 'leaky bucket' algorithm. Two values define the algorithm behavior:
		+	* (A) Maximum calls per second
		+	* (B) Maximum calls burst
		+	Tokens are added to the bucket at a regular rate of (A) per second, until the bucket contains a maximum of 'B' tokens.
		+	When an incoming call is received, or outgoing call needs to be made, a token is taken from the bucket, or the call is refused if the bucked is empty.
		+
		+	This allows to absorb call bursts of up to (B) consecutive calls without dropping any calls, and also protects from an average call rate that's higher than (A) calls per second.
		+
		+	=== Typical usage ===
		+	Call rate limiting is generally used to avoid overloading a system's CPU (local TMedia unit or remote system) by sending too many calls per second.
		+	Local system is generally protected using a per-adapter limit.
		+	Remote system is generally protected using a per-NAP limit.
		+
		+	Maximum simultaneous calls limit is generally used to protect a NAP from being overloaded. It's frequently used for SIP NAPs to avoid RTP bandwidth to exceeds the capacity of the IP network. It's less frequently used for ISDN, CAS or SS7 as the number of CICs in the NAP already provides a limit to the number of simultaneous calls.

	== References ==		== References ==

@@ Line 81: / Line 81: @@
 *[[TMG5800]]: 70 BCPS
 *[[TMG7800]]: 670 BCPS
 [[category:Needs revising]]