Jump to: navigation, search

Media Control Platform Capacity Testing (Physical Servers Running Windows)

This table does not focus on GVP as a whole, but rather shows the impact of media services (announcements, call parking, bridging, conferencing, transcoding and video) on the performance of the Media Control Platform (MCP).

Application Type Hardware Peak CAPS Peak Ports Comment
Audio bridge transfer
G711u <-> G711u (baseline ~117 seconds duration)
Quad-Core Xenon 5355 2.66GHz 6.8 800 Bi-directional audio streams. Tested on Windows 2003.
Transcoding with bridge transfer
G711u <-> AMR (~117 seconds duration )
Quad-Core Xenon 5355 2.66GHz 2.6 300 Bi-directional transcoding. Tested on Windows 2003.
Transcoding with bridge transfer
G711u <-> AMR-WB (~117 seconds duration )
Quad-Core Xenon 5355 2.66GHz 2.0 230 Bi-directional transcoding. Tested on Windows 2003.
Transcoding with bridge transfer
G711u <-> G722 (~117 seconds duration )
Quad-Core Xenon 5355 2.66GHz 3.0 350 Bi-directional transcoding. Tested on Windows 2003.
Transcoding with bridge transfer
G711u <-> G726 (~117 seconds duration )
Quad-Core Xenon 5355 2.66GHz 2.6 300 Bi-directional transcoding. Tested on Windows 2003.
Transcoding with bridge transfer
G711u <-> G729 (~117 seconds duration )
Quad-Core Xenon 5355 2.66GHz 3.0 350 Bi-directional transcoding. Tested on Windows 2003.
SRTP with bridge transfer – G.711u (~67 seconds duration) Quad-Core Xenon 5355 2.66GHz 18 1200 The capacity is the same for RTP and SRTP of both encryption and decryption, one direction only of audio stream. Tested on Windows 2003.
MSML CPD + VXML dialog (helloworld)
( 8 seconds overall call duration which includes 2.5 seconds CPD time)
Quad-Core Xenon 5355 2.66GHz 30 n/a CPD enabled within MSML which also invoke a VXML dialog using default helloworld page. VXML dialog will start after CPD result returned the result of human successfully.
Netann announcement – 3 seconds audio Quad-Core Xenon 5355 2.66GHz 120 (preferred) 200 (peak) 500 (preferred) 1100 (peak) Preferred – with call setup + call tear down latency < 1sec (500ms each)
Peak – ignore call setup/tear down delay
Netann announcement – 10 seconds audio Quad-Core Xenon 5355 2.66GHz 90 (preferred) 150 (peak) 900 (preferred) 1500 (peak) Preferred – with call setup + call tear down latency < 1sec (500ms each)
Peak – ignore call setup/tear down delay
Netann Play Treatment - G.711u, G.729, GSM (~60 seconds audio) Quad-Core Xenon 5355 2.66GHz 30 1800 No transcoding. The capacity is the same for G.711u, G.729, or GSM. Tested on Windows 2003.
Netann 2 party Call Recording - G.711u (~60 seconds duration) Quad-Core Xenon 5355 2.66GHz 12 720 call legs (360 recording sessions) Tested on Windows 2003.
Netann 2 party Call Recording - G.729 (~60 seconds duration) Quad-Core Xenon 5355 2.66GHz 9 540 call legs (270 recording sessions) Tested on Windows 2003.
Netann 2 party Call Recording - GSM (~60 seconds duration) Quad-Core Xenon 5355 2.66GHz 8 480 call legs (240 recording sessions) Tested on Windows 2003.
MSML Conference (all participants using the same codec) – G711u, G.729, GSM (3-party; ~60 seconds duration) Quad-Core Xenon 5355 2.66GHz 6 360 participants (120 conference sessions) The capacity is the same for G.711u, G.729, or GSM. Tested on Windows 2003.
MSML Conference (different codecs between participants) – G711 and G.729 (3-party; ~60 seconds duration) Quad-Core Xenon 5355 2.66GHz 6 360 participants (120 conference sessions) Tested on Windows 2003.
MSML Conference (different codecs between participants) – G711 and GSM (3-party; ~60 seconds duration) Quad-Core Xenon 5355 2.66GHz 6 360 participants (120 conference sessions) Tested on Windows 2003.
MSML Conference (3-party conference; all participants using the same code – G711, HR Timer disabled ~60 seconds duration) 1x Hex-Core Xeon X5670 2.93GHz 6 360 participants (120 conference sessions) Tested on Windows 2008 R2 x64 SP1 with HR Timer disabled in 8.1.6.
MSML Conference (3-party conference; all participants using the same code – G711, HR Timer enabled ~60 seconds duration) 1x Hex-Core Xeon X5670 2.93GHz 5 300 participants (100 conference sessions) Tested on Windows 2008 R2 x64 SP1 with HR Timer enabled in 8.1.6.
MSML Conference (One giant conference with 3 speakers; all other participants are listeners. Each participant stays 1800 secs (30 mins) in the conference. Codec G.711) 1x Six-Core Xeon X5675 3.06GHz 0.72 1300 participants (1 conference session) Tested on Windows 2008 Server R2 x64 SP1 with only one MCP instance. Threaded outputs enabled (conference.threadedoutputs = true).
MSML Conference (One giant conference with 3 speakers; all other participants are listeners. Each participant stays 1800 secs (30 mins) in the conference. Codec H263 + G.711) 1x Six-Core Xeon X5675 3.06GHz 0.61 1100 participants (1 conference session) Tested on Windows 2008 Server R2 x64 SP1 with only one MCP instance. Threaded outputs enabled (conference.threadedoutputs = true).
MSML Conference (One giant conference with 3 speakers; all other participants are listeners. Each participant stays 1800 secs (30 mins) in the conference.
Codec G.711, HR Timer disabled & gain control enabled)
1x Six-Core Xeon X5670 2.93GHz 0.72 1300 participants (1 conference session) Tested on Windows 2008 Server R2 x64 SP1 with only one MCP instance. Threaded outputs enabled (conference.threadedoutputs = true).
MSML Conference (One giant conference with 3 speakers; all other participants are listeners. Each participant stays 1800 secs (30 mins) in the conference.
Codec G.711, HR Timer enabled & gain control enabled)
1x Six-Core Xeon X5670 2.93GHz 0.56 1000 participants (1 conference session) Tested on Windows 2008 Server R2 x64 SP1 with only one MCP instance. Threaded outputs enabled (conference.threadedoutputs = true).
MSML Conference (One giant conference with 3 speakers; all other participants are listeners. Each participant stays 1800 secs (30 mins) in the conference.
Codec G.711, HR Timer enabled & gain control disabled)
1x Six-Core Xeon X5670 2.93GHz 0.78 1400 participants (1 conference session) Tested on Windows 2008 Server R2 x64 SP1 with only one MCP instance. Threaded outputs enabled (conference.threadedoutputs = true).
MSML Conference (One giant conference with 3 speakers; all other participants are listeners.
Each participant stays 1800 secs (30 mins) in the conference.
Codec G.711, HR Timer disabled & gain control disabled)
1x Six-Core Xeon X5670 2.93GHz 0.99 1800 participants
(1 conference session)
Tested on Windows 2008 Server R2 x64 SP1 with only one MCP instance.
Threaded outputs enabled (conference.threadedoutputs = true).
Note:
  • Preferred means the highest capacity that the system can sustain while maintaining optimal user experience.
  • Peak means the highest capacity that the system can sustain regardless of the user experience.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on July 11, 2018, at 00:47.