Hardware: Difference between revisions

From VoIPmonitor.org
Jump to navigation Jump to search
No edit summary
No edit summary
 
(8 intermediate revisions by 2 users not shown)
Line 2: Line 2:


== 17000 concurrent calls peak ==
== 17000 concurrent calls peak ==
network throughput ~2.8Gbit


=== hardware ===
=== hardware ===
  2x Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz   
  2x Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz   
Intel 82599ES 10-Gigabit SFI/SFP+


=== voipmonitor.conf ===
=== voipmonitor.conf ===
Line 26: Line 29:
==== mysql ====
==== mysql ====
  90 days - 1.5TB
  90 days - 1.5TB
==== spool pcap ====
8 days RTP+SIP - 21TB


== 200 concurrent calls ==
== 200 concurrent calls ==


=== hardware === Intel(R) Xeon(R) CPU          E5520  @ 2.27GHz
=== hardware ===  
 
Intel(R) Xeon(R) CPU          E5520  @ 2.27GHz
 
=== voipmonitor.conf ===
 
savesip = yes
savertp = yes
pcap_dump_zip_rtp = lzo (default RTP LZO compression)
 
=== CPU used ===
 
==== voipmonitor process ====
~88% (1 cpu cores)
 
 
==== mysql process ====
~2%
 
 
=== memory used ===
~298MB for voipmonitor process
 
 
=== disk usage ===
 
==== mysql ====
 
30 days - 7.5GB
 
 
 
 
 
= Space estimation =
== spooldir size - space for packets records ==
with default compression settings of voipmonitor you can count aprox 1MB/1minute of 2RTP streams (1 leg with g711 codec), if you have 2legs per call you can count aprox 2MB/1minute of record (SIP+RTP+flow charts)
== CDR space for mysql's datadir ==
For database you can count very aprox. 2KB per CDR record with default table compression enabled (default mysqlcompress = yes in /etc/voipmonitor.conf)
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


=== voipmonitor.conf === savesip = yes savertp = yes pcap_dump_zip_rtp = lzo (default RTP LZO compression)
.
=== CPU used ======= voipmonitor process ==== ~88% (1 cpu cores) ==== mysql process ==== ~2% === memory used === ~298MB for voipmonitor process=== disk usage ======= mysql ==== 30 days - 7.5GB

Latest revision as of 10:59, 27 July 2018

hardware sizing examples

17000 concurrent calls peak

network throughput ~2.8Gbit

hardware

2x Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz  
Intel 82599ES 10-Gigabit SFI/SFP+

voipmonitor.conf

savesip = yes
savertp = yes
pcap_dump_zip_rtp = lzo (default RTP LZO compression)


CPU used

voipmonitor process

~1300% (13 cpu cores) 


mysql process

~300% (3 cpu cores)

memory used

~7000MB for voipmonitor process

disk usage

mysql

90 days - 1.5TB

spool pcap

8 days RTP+SIP - 21TB

200 concurrent calls

hardware

Intel(R) Xeon(R) CPU E5520 @ 2.27GHz

voipmonitor.conf

savesip = yes
savertp = yes
pcap_dump_zip_rtp = lzo (default RTP LZO compression)

CPU used

voipmonitor process

~88% (1 cpu cores) 


mysql process

~2% 


memory used

~298MB for voipmonitor process


disk usage

mysql

30 days - 7.5GB



Space estimation

spooldir size - space for packets records

with default compression settings of voipmonitor you can count aprox 1MB/1minute of 2RTP streams (1 leg with g711 codec), if you have 2legs per call you can count aprox 2MB/1minute of record (SIP+RTP+flow charts)

CDR space for mysql's datadir

For database you can count very aprox. 2KB per CDR record with default table compression enabled (default mysqlcompress = yes in /etc/voipmonitor.conf)




































.