From Meeting Server version 2.4, you can configure the recording resolution of the Recorder on the Recorder component itself.
To configure the resolution use the MMP command: recorder resolution <audio|720p|1080p>
If no resolution is configured, the default setting is 720p30. A setting of 1080p only records 1080p30, it does not support 720p60. Audio recordings are stored in .mp4 file format.
Note: XMPP is removed from version 3.0. The internal XMPP recorder and streamer components are replaced with new internal SIP recorder and streamer components.
Using the internal XMPP recorder component (up to version 2.9)
The table below provides typical specifications for the different recorder settings, the recommendations are based on our internal testing for versions up to 2.9.
Recorder setting | % of physical core per recording | RAM required per recording | Typical disk usage per hour | Planned disk usage per hour (recommended) |
720p | 50% | 0.5GB | 300MB to 800MB | 1GB |
1080p | 100% | 1GB | 1GB to 1.6GB | 2GB |
audio | 20% | 125MB | 70MB | 100MB |
Using the internal SIP recorder component (from version 3.0)
The table below provides typical specifications for the different recorder settings, the recommendations are based on our internal testing for versions from 3.0. The recommended deployment for production usage of the recorder is to run it on a dedicated VM with a minimum of 4 vCPU cores and 4GB of RAM. The following table provides an idea of performance and resource usage for each of the recording types.
Recorder setting | Recordings per vCPU | RAM required per recording | Disk budget per hour | Maximum concurrent recording |
720p | 2 | 0.5GB | 1GB | 40 |
1080p | 1 | 1GB | 2GB | 20 |
audio | 16 | 100MB | 150MB | 100 |
Key point to note (applies to new internal SIP recorder component only):
- Performance scales linearly adding vCPUs up to the number of host physical cores
See your Deployment Guide for more information on recording and set up.
- Last update:
- 17-Sep-2020
- FAQ ID:
- 1406