Server Sizing Concept

Determine your server configuration (components and the number of units) depending on 1) required hard disk capacity and 2) video data volume per second.

1) Required hard disk capacity: Consider the required hard disk capacity based on continuous recording with fixed frame rate, resolution, and quantity.

2) Video data volume per second: If the video data volume per second by server exceeds values shown below, you should consider multiple servers or review the recording conditions.

Note

• Every operation environment of VK-64/VK-16 is different (due to different requirements and different hardware specifications) and the figures provided below are just for the reference.
• Data volume per drive should be less than 2TB.

Approximate Video Data Volume per Second

The recording performance of VK-64/VK-16 v2.2 is as follows.

• For dedicated Storage Server: Maximum amount of recorded data per server = 5.5 MB/sec or less (when using SCSI, SAS disk)

• For Storage and Playback Server: Maximum amount of recorded data per server = 3 MB/sec or less

Note

Data-writing performance may be reduced than the approximate values given above depending on the hard disk or the RAID card in the PC.

Required Hard Disk Capacity

The size of the images varies depending on the configuration of the Camera Server (the settings for Quality and Resolution) and the complexity of the actual image.

Determining Required Hard Disk Capacity

Determine the required hard disk capacity as follows.

1. Determine the required number of Camera Servers and required video data size.

2. Select the Image Quality of each Camera Server.

The video quality improves in proportion to the set value, but the data volume also becomes larger.

3. Determine the frame rate for recording video (i.e., the number of frames per second).

For general security purposes, 1 to 2 fps is common. Higher frame rate requires more hard disk space.

4. Determine the recording period per day and duration to retain data.

5. After determining the conditions above, calculate the required hard disk capacity due to the video data size (in KB).

6. If you record audio, to calculate the amount of hard disk space required for the audio data. The data size for recording audio is 8 KB/s regardless of the type of Camera Server.

When determining hard disk sizes it is important to take into account that there needs to be considered about 10 to 20% additional room.

Example 1: JPEG recording

• Using 16 Camera Servers (VB-C60) for recording,
• With each camera set to Medium Size for video data size and Image Quality set to 50 (data size per 1 rame: 15KB),
  • Recording frame rate is set at 2 fps, and
  • Data size per second is approximately 30 KB (= 15 KB x 2fps).

Although actual data size depends on objects shot by each Camera Server, this calculation assumes the typical size shown above.

• Audio recording as also performed simultaneously on 2 of the Camera Servers.

For the above configuration, when JPEG images from 16 camera servers are being recorded continuously at frames per second all day, every day, the required hard disk space is approximately 40GB per day (=30KB x 16 cameras x 60 seconds x 60 minutes x 24 hours = 41472000KB per day). When audio is recorded by 2 camera server, the required hard disk space is approximately 1.3 GB per day (=8 KB x 2 units x 60 seconds x 60 minutes x 24 hours = 1382400 KB).

Example 2: MPEG-4 recording

• Using 8 Camera Servers (VB-C60) for recording,
  • With each camera set to Medium Size (320 x 240) and Video Quality is set to 3,
  • Recording frame rate is set at 30 fps, and
  • Data size per second is approximately 30 KB.

Although actual data size depends on objects shot by each Camera Server, this calculation assumes the typical size shown above.

For the above configuration, when MPEG-4 video from 8 Camera Servers are being recorded continuously at 30 fps all day, every day, the hard disk space required is approximately 40GB per day (=60KB x 8 cameras x 60 seconds x 60 minutes x 24 hours = 41472000KB per day).

* For the above figures please note that the bandwidth is calculated as 1000Kbps = 1Mbps, and the disk size as 1024KB = 1MB.

The following tables give some typical data sizes per frame (in kilobytes) for various combination of quality and resolution values referring to a VB-C500VD, VB-C500D, VB-C60, VB-C300 and VB-C50i.

However the actual data size may be different from the data size in the table below depending on the weather condition and complexity of the image. For example, images of an empty corridor would typically be smaller than these values and images of an intricate pattern such as a crowded shopping mall may be larger than these.

* All of the data in the previous page sizes are only rough guide, and may increase or decrease depending on the object being shot. Please be sure to confirm under the actual installation conditions before starting operations. Select [Video Information] from the [View] menu of the Viewer (bundled with the Camera Server) to check the data quantity per frame (VB-C300, VB-C50i, VB-C50iR, VB-C50FSi).

Note

Please note that data size may increase enormously when video quality is set to 100 with the VB-C50i, VB-C50iR, VB-C50FSi, VB-C50Fi.

The size of audio data is 8 KB/s.

Sensor Event Recording and Motion Detection Recording Concept

Notes on Sensor Event Recording and Motion Detection Recording

• When an event, such as sensor input or motion detection, occurs, video data will be stored in the Storage Server as an operation record.
• As the number of stored operation records increased, the operation and search speed at event detection and response speed of viewers may be affected.

Notes on Motion Detection Recording

• The Motion Detection function detects motion where no motion occurred before. Do not use this function where the motion detection may operate too frequently, e.g., where many people pass through.
• Motion detection should be set on the Camera Server. If motion detection is set on the Storage Server, the processing load on the PC will increase, and this may have an effect on the storage performance. (except VB-C300)

Storage Server Performance

Note

• These data above are rough guide. As many factors can influence the actual performance possible (including networking equipment, disk write speed, complexity of camera image, etc), the actual performance of VK-64/VK-16 recording in a specific installation will vary. Please be sure to confirm under the actual installation conditions before starting operations.
• If there are many registered Camera Servers, it is recommended that you use two or more PCs or configure to use the Layout frequency.

Notes on Storage Server Operation

It is recommended to use the Storage Server exclusively for the VK-64/VK-16.

Be sure to avoid the following forms of operation.

• Using the Storage Server with a Web Server
  • As Storage Server, you cannot use a PC where Web server software such as Windows standard IIS (Internet Information Server) or Apache has been already installed.
  • Since the Storage Server uses the HTTP protocol to communicate with the Camera Server, therefore it may not work properly if other Web applications exist on the same platform.
  • The HTTP port number used by the VK-64/VK-16 should be fixed to "80".
• Using the Storage Server with a Database Server (e.g., SQL Server, Oracle)
  • If the hard disk is heavily loaded in database processing, recording may not work normally. Conversely, the database server may be affected by the VK-64/VK-16 when it need hard disk performance to complete its task.
• Using the Storage Server with a File Server
  • Accesses to the hard disk may be too frequent and recording may not work normally. Also, the disk capacity for the VK-64/VK-16 may run short.
• Using the Storage Server with other applications
  • The processing load of other applications may have a negative effect on the storage performance.
  • This software uses 3 ports: TCP 80/TCP 9080/TCP 10080. If you are running another application which uses the same ports on your PC at the same time, please use another port.

Notes on Viewer Sizing

Consider the following points when selecting the PC for viewer (installed).

• Live-video viewing and recorded video playback performance of the VK-64/VK-16 largely depends on the CPU and graphics board performance on the PC. The CPU performance affects image capturing and video data generation, and the graphics board performance affects image drawing.

See the following example when selecting the PC for the viewer installed.

In this example, the OS is Windows XP Professional.

1. CPU: Pentium 4 3.0GHz, memory: 1GB, graphics board: Quadro FX570 When using the VB-C60 with Resolution=340 x 240 and Quality=3:

Total frame rate:

JPEG image---Max. 220 fps

MPEG-4 video---Max. 180 fps

2. CPU: Pentium 4 3.6GHz, memory: 1GB, graphics board: Quadro FX1700 When using the VB-C60 with Resolution=340 x 240 and Quality=3:

Total frame rate:

JPEG image---Max. 260 fps

MPEG-4 video---Max. 210 fps

3. CPU: Pentium 4 3.8GHz, memory: 1GB, graphics board: Quadro FX1700 When using the VB-C60 with Resolution=340 x 240 and Quality=3:

Total frame rate:

JPEG image---Max. 280 fps

MPEG-4 video---Max. 240 fps

Tip

• The total frame rate is calculated as: Number of Camera Servers in the Viewer window x Frame rate. That means, with 10 Camera Servers and 10 fps frame rate, the total frame rate is 100 fps.
• Note that the total frame rate above varies depending on the combination of the PC and graphics board. It is also affected by other applications (e.g., anti-virus application) running on the same PC.
• When displaying MPEG-4 video in VGA, the maximum frame rates are the one-forth of the above frame rates.

Network Bandwidth Concept

You should consider the network bandwidth when recording video or viewing live video from the network camera.

The network bandwidths should be calculated separately for recording and live viewing.

Example:

With one recording server (QVGA, 1 fps) and two live viewing servers (QVGA, 5 fps):

• Bandwidth for recording

15 (KB/frame) x 1 (frame/sec) x 8 (bits) = 120 Kbps

• • Bandwidth for live viewing (per server)

15 (KB/frame) x 5 (frame/sec) x 8 (bits) = 600 Kbps

Therefore, required network bandwidth is calculated as follows:

120 Kbps x 1 + 600 Kbps x 2 = 1320 Kbps = Approx. 1.3 Mbps

Note that the line speed unit is bps (bits per second).