Kofax Communication Server 10.0.0 - Manual (Page 28)

Environment Guide Version 10.00.00
28 © Copyright Kofax. All information is subject to change without notice.
Average counters (“Avg.”) indicate the average of the particular value between two subsequent
performance monitor measures.
Peak counters (“Peak”) indicate the peak value between two subsequent performance monitor measures.
After the deployment has been already done, it is necessary to continue observing the actually used
resources of the particular TCOSS Server configuration and adapt the resources allocation if necessary.
Please refer to the chapter Virtualized Operation.
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).
Resources Estimation and Key Performance Indicators for IPPrinter
Receiving fax channels [x]/
Printouts in fax pages / minute
IPPrinterMetrics
10
20 fax pages / min 20
40 fax pages / min 30
60 fax pages / min
Resource capacity to be planned on the ESX server:
CPU [MHz]
1000 1200 1400
RAM [MByte]
(1)
1024 1024 1024
Average IPPrinter disk kBytes/s 100 125 150
Average IPPrinter disk IOPS/s 22 24 28
Average network kBytes/s 70 90 110
Key performance indicators that must be measured and fulfilled for the proper operation:
none
(1) If more than 1 IPPrinter instance is being used 2048 MByte RAM should be planned
5.3 Virtualization Deployment
This chapter provides a short overview on different possibilities how to deal with system resources on the
ESX host.
5.3.1 CPU
The ESX server handles the CPU resources in terms of “MHz bandwidth” by simply adding the MHz CPU
cycles of all available CPUs together (e.g. having 4 dual-core 3.6 GHz CPUs in the ESX server would give
total CPU bandwidth of 4x2x3600=28800MHz). There are two possibilities how to allocate this CPU
bandwidth to the particular VM: