Difference between revisions of "H323 pass-through test"
From Kolmisoft Wiki
Jump to navigationJump to search
| Line 34: | Line 34: | ||
=== Conclusion === | === Conclusion === | ||
We reached | We reached 250 sim. calls. | ||
Tests shown that 1 H323 pass-through call takes ~1% of CPU power of this server. | Tests shown that 1 H323 pass-through call takes ~1% of CPU power of this server till calls reach 120 sim. calls. After that CPU %/call starts increasing. | ||
Under 260 calls server Asterisk starts to kill calls: [[Image:aste]] | |||
[[Image:h323test_chart.png]] | [[Image:h323test_chart.png]] | ||
=== Screenshots === | === Screenshots === | ||
Revision as of 14:48, 8 February 2009
Server
- Intel® Xeon® Processor 5030 (4M Cache, 2.66 GHz, 667 MHz FSB)
- 4 gb ram
- Hardware RAID 10 128 MB cash SATA 4 x 250 GB 7200 RPM
- Asterisk 1.4.18.1
- MOR 0.8 pre17
- Protocol: H323
- Codec G711
- The NuFone Network's OpenH323 Channel Driver
- openh323_v1_18_0
- pwlib_v1_10_0
- Test schema: originator(playback) ---> Our test server ---> terminator(playback)
Call file used
Channel:Local/99555272804@mor MaxRetries:1 RetryTime:60 WaitTime:30 Account:2823 Context:test Extension:111 Priority:1
Conclusion
We reached 250 sim. calls.
Tests shown that 1 H323 pass-through call takes ~1% of CPU power of this server till calls reach 120 sim. calls. After that CPU %/call starts increasing.
Under 260 calls server Asterisk starts to kill calls: File:Aste
Screenshots
- top, 10 calls
- top, 20 calls
- top, 30 calls
- top, 40 calls
- top, 50 calls
- top, 60 calls
- top, 70 calls
- top, 80 calls
- top, 90 calls
- top, 100 calls
- asterisk, 100 calls
- top, 110 calls
- top, 120 calls
- asterisk, 120 calls
