Disk space requirements

Link copied to clipboard

When buying hardware for your servers, you obviously want to be sure that their capability will be sufficient to suit the demands of your business. Among other hardware requirements, the HDD capacity should be carefully considered to ensure that it will satisfy the desired traffic patterns as well as future business growth opportunities.

Disk space requirements can be estimated based on business scenarios, traffic patterns and the desired PortaSwitch configuration. Consider the examples below.

PortaBilling, PortaSIP and log storage servers

Link copied to clipboard

We will use the following figures to estimate the disk space required:

  • Each call processed by PortaSwitch will increase SIP logs by approximately 100 KB and billing logs by approximately 50 KB.

  • Each registration processed by PortaSwitch will increase SIP logs by approximately 10 KB and billing logs by approximately 5 KB.

We will also use the following assumptions for the sake of simplicity:

  • The average call duration is around 5 minutes.

  • A call success rate (ASR) is 50% (the industry norm).

  • There are ten thousand registered phones with an average re-registration period of 5 minutes.

  • The PortaSIP server and the PortaBilling servers contain uncompressed log files for the last three days and all log files for the required period (e.g., 10 days) will be available on the centralized log storage (7 compressed and 3 uncompressed).

  • Log compression ratio is 5% (bzip2).

Using the figures and assumptions described above, we can estimate how much disk space is needed to process 10 MMM (ten million minutes per month). Taking into consideration that for every failed call, logs and xDRs are also generated, we need to multiply the total sum by two (ASR 50%). Note that we calculate an average number of calls per day using the following formula: 10,000,000 minutes / 5 minutes / 30 days = 66,666 calls and then round up this number to 70,000, for convenience.

  • PortaBilling:
    • Calls: 70,000 calls per day * 50 KB * 2 ≈ 7 GB for one day

    • Registrations: 288 registrations / day per phone * 10,000 phones * 5 KB ≈ 14.4 GB for one day

    • Total for one day: 7 GB + 14.4 GB = 21.4 GB

    • Total for three days: 21.4 GB * 3 days ≈ 64.2 GB

  • PortaSIP:
    • Total for three days: ≈ 42.8 * 3 days ≈ 128.4 GB

    • Total for one day: 14 GB + 28.8 GB ≈ 42.8 GB

    • Registrations: 288 registrations / day per phone * 10,000 phones * 10 KB ≈ 28.8 GB for one day

  • The centralized log storage:

    3 days * (21.4 GB + 42.8 GB) + 7 days * (21.4 GB + 42.8 GB) * 5% ≈ 192.6 GB + 22.5 GB ≈ 215 GB

Database servers

Link copied to clipboard

We will use the following figures to estimate how much disk space is needed on the database servers:

  • Each xDR takes up about 1.5 KB database space.

  • PortaBilling produces at least 2 xDRs for each call. Actually, the number of xDRs produced depends on the call scenario and can reach up to 5–7 or even more xDRs for complex calls. For simplicity’s sake, we assume that on average, 3 xDRs are produced per call.

We will also use the following assumptions for the sake of simplicity:

  • The average call duration is around 5 minutes.

  • A call success rate (ASR) is 50% (the industry norm).

  • You will need to allocate space for MySQL binary log files (25–100 GB depending on the rate of usage of the database). Let’s allocate 50 GB for binary log files.

  • In addition, for performing operations such as backup, you will need to reserve an amount of free space roughly equal to the projected database size.

  • You will keep xDRs for the previous 60 days.

Using the figures and assumptions described above we can estimate the disk space that will be consumed to process 10 MMM (ten million minutes per month) on the database servers:

  • 70,000 calls per day * 1.5 KB * 3 CDRs * 60 days * 2 * 2 ≈ ≈ 75.6 GB

So, not taking into the consideration the MySQL binary log files and reserving space for operations such as backup, 75.6 GB is required on the database servers to process 10 MMM.

Estimates based on different traffic patterns

Link copied to clipboard

The following table shows the minimum amount of disk space required on each server for installations with different traffic patterns. This includes the 60 GB minimum necessary for system installation.

Traffic pattern

The database servers

PortaBilling server

PortaSIP server

The centralized log storage server

keep logs for last two days only

 

10 MMM, 10,000

registered phones

185 GB

124 GB

188 GB

275 GB

20 MMM, 20,000

registered phones

260 GB

188 GB

316 GB

490 GB

50 MMM, 50,000

registered phones

485 GB

220 GB*

273 GB**

1 TB

100 MMM, 100,000 registered phones

860 GB

380 GB*

487 GB**

2.2 TB

* If two PortaBilling servers provide AAA services, then this amount of disk space will be needed on each server.

** If three PortaSIP servers process traffic, then this amount of disk space will be needed on each server.

The above figures are minimal and depending on the services provided, may grow (e.g., call records take up disk space. In order to store 15 hours of recorded conversations, 1 GB of disk space is required).

On this page