Kofax Communication Server 9.2.0 - Manual (Page 32)

Environment Guide Version 9.02.00
32 © Copyright Kofax, Inc. All information is subject to change without notice.
Following resource estimation and key performance indicators table was measured under similar
circumstances as the TCOSS resource estimation table in previous chapter, with the following differences:
1. Single TCOSS instance was used and the TC/FoIP process was running on the same VM
2. The first half of the configured FoIP channels (10, 20 and 30) were sending faxes through Cisco 28xx
gateway which was connected via 30-channels PRI trunk with the standard Siemens Hicom 300 PBX
3. The PBX routed these faxes back to the PRI trunk and thus they were received with the second half of
the FoIP channels
Resources Estimation and Key Performance Indicators for TC/FoIP (running on the TCOSS VM)
Load fax channels [x]/ Printouts in
fax pages / minute
TC/FoIP Metrics
10
20 fax pages / min
20
40 fax pages / min 30
60 fax pages / min
Required granted resources on the ESX server:
CPU [MHz]
(1)
1600 1800 2000
RAM [MByte] 512 512 512
Resource capacity to be planned on the ESX server:
Average TCOSS Disk kBytes/s
25 50 75
Average TCOSS Disk IOPS/s 6 12 18
Average Network kBytes/s
(2)
20 40 60
Network bandwidth [Mbit/s]
(2)
10 10 10
Key performance indicators that must be measured and fulfilled for the proper operation:
Average RTT
FoIP
[ms] 100 100 100
Peak RTT
FoIP
[ms] 1000 1000 1000
Average Write Disk Latency [ms] 25 25 25
Peak Write Disk latency [ms] 100 100 100
(1) In the case Tc/FoIP is running in the dedicated VM (without TCOSS), the required CPU bandwidth may
be decreased by 400MHz, e.g. for 30 channels it would be 2000-400=1600MHz.
(2) Average Network kBytes/s is the real bandwidth consumption, the Network bandwidth is the
recommended capacity to be planned for the TCOSS server
Refer to the previous chapter for the mapping among key performance indicator and Windows performance
counter names.
IPPrinter
This chapter provides resource estimation of the ESX Server resources (CPU, RAM, Disk and Network) for
a typical IPPrinter VM printing received 2-page faxes (ca. 100kByte TCI code) via particular number of fax
channels (e.g. 10, 20, 30).
Note that this is planning stuff only, no granted resources are required. However, the IPPrinter is very CPU-
bound (causes high CPU utilization) and that is why its operation must be carefully observed while running
in the virtualized environment. If any problem would be noticed (e.g. incoming faxes being printer with a
long delay after being received) it may indicate that IPPrinter would not get enough CPU resources. In such
a case necessary CPU bandwidth should be granted for the IPPrinter VM (based on estimated in the table
below or even more if necessary).