Optimal Values of and Limitations on the System Performance
|Influencing factors||Optimal values & limitations||Comments|
|System performance in pages per 24 hours||
FlexiCapture is able to process:
|Number of scanning operators||FlexiCapture is able to host 1000 scanning operators.||This value is mostly limited by the amount of traffic produced on peaks and on average – see this section for more information.|
|Number of verification operators||FlexiCapture is able to host 500 verification operators.||We assume that the load on the System generated by 5 verification operators equals the load generated by one core on a Processing Station. This assumption can be used to calculate the maximum allowed number of verifiers based on the results of unattended processing tests. See this section for more information.|
|Number of processing stations||We used up to 200 cores in total for all Processing Stations.||This depends greatly on the power of the Application Servers and on how long it takes to process one task at a Processing Station. See this section for more information.|
|Number of cores per Processing Station||
With regular disk drive (SATA2 7 500 rpm): up to 8 logical cores.
With fast disk drive (SAS 15 000 rpm): up to 16 logical cores.
With RAM drive: up to 32 logical cores.
|Number of pages in a batch||Optimal value is from 10 to 1000 pages in a batch.||
Small batches (3 pages or fewer) cause too much processing overhead per page, so the total performance in pages in 24 hours goes down. In particular, the Processing Server’s maximum number of cores may go down because of the tasks are too small.
Very large batches (2000 pages and more) provide too big a load on the Application Server and Database when routing from stage to stage. They can also face timeout and maximum request size limitations in the network and underlying software settings.
|Number of pages in a document||Optimal value is up to 100 pages in a document||Large documents can cause slowness in operators’ work: it takes a long time to load all images of pages and calculate rules that use a large number of fields, e.g. large multipage tables.|
|Number of pages, documents, and batches in the system||This highly depends on hardware used. For a Large configuration, up to 100,000 batches, or 1 mln documents, or 10 mln pages is normal.||A very large number of pages, documents, and batches in the System may lead to the Database Server acting on queries more slowly. We recommend then using more powerful hardware for the Database Server and periodically rebuilding indexes for tables.|
|Data storage time||
Typically, pages, document, batches and event log records are stored in the System for up to 2 weeks.
Statistics for reporting can be stored for years with no impact on performance.