Improving Performance
When configuring your FortiRecorder appliance and its features, there are many settings and practices that can yield better performance.
Video performance
Video performance is a combination of the video input (from the cameras) and the video output (to the browser for live views and playback).
Input performance factors
- Peak number of cameras streaming to the FortiRecorder simultaneously
- The camera recording type (motion detection only or continuous)
- The camera resolution, frame rate, and image quality
Output performance factors
- Number of administrator/operator sessions
- Number of live camera views per administrator/operator session
- Peak number of simultaneous administrator/operator live views
Resolution has the largest impact on the overall FortiRecorder performance.
- Low resolution — n MB/s
- Medium resolution — 2n MB/s
- High resolution — 6n MB/s
In other words, high resolution video will generate 3 times as much raw data as the default, medium resolution. Depending on how efficiently a specific raw stream can be compressed, higher resolutions can multiply the bandwidth and/or disk space required per camera, and per login session. For example, assuming a FortiCam 20A camera, the FortiRecorder can store on its local hard drive about 36 days’ worth of high resolution video, but about 240 days’ worth of low resolution video.
Degree of motion in the camera’s field of view also affects video performance. Constant and/or extreme motion will result in larger files/streams, because the compression method cannot encode it as efficiently. To improve compression, exclude areas of irrelevant motion such as fans or blinking lights from the camera’s field of view.
For sizing guidelines and estimates on the amount of video that you will be able to store, contact your reseller. Alternatively, expand your storage by configuring a network storage location (see “External storage”).
System performance
- Delete or disable unused cameras. FortiRecorder allocates memory with each camera, regardless of whether it is actually in active use. Configuring extra cameras will unnecessarily consume memory and decrease performance.
- To reduce latency associated with DNS queries, use a DNS server on your local network as your primary DNS.
Logging and alert performance
If you have a FortiAnalyzer, store FortiRecorder’s logs on the FortiAnalyzer to avoid resource usage associated with writing logs to FortiRecorder’s own hard disks. See the Configuring Log Settings chapter.
If you do not need a log or alert, disable it to reduce the use of system resources.
Reduce repetitive log messages. Use the alert email settings, to define the interval that emails are sent if the same condition persists following the initial occurrence. See the chapter on Configuring Alert Email.
Avoid recording log messages using low severity thresholds, such as information or notification, to the local hard disk for an extended period of time. Excessive logging frequency saps system resources and can cause undue wear on the hard disk and may cause premature failure.
Packet capture performance
Packet capture can be useful for troubleshooting but can be resource intensive. (See “Packet capture”.) To minimize the performance impact on your FortiRecorder appliance, use packet capture only during periods of minimal traffic. Use a local console CLI connection rather than a Telnet or SSH CLI connection, and be sure to stop the command when you are finished.