...
Estimated GlobalCapture Throughput
(From Mike King. Note that these are rough estimates only, for GlobalCapture v2.0.2. Customer documents, hardware, software, and connectivity can cause throughput to vary widely.)
| Cores | 4 Hours | 8 Hours | Month | Year |
| Single | 500 pages | 1000 pages | 20,833 pages | 250,000 pages |
| Dual | 1000 pages | 2000 pages | 41,666 pages | 500,000 pages |
| Tri | 1500 pages | 2000 pages | 62,500 pages | 750,000 pages |
| Quad | 2000 pages | 4000 pages | 83,333 pages | 1,000,000 pages |
| Eight | 4000 pages | 8000 pages | 166,666 pages | 2,000,000 pages |
| Twelve | 6000 pages | 12,000 pages | 250,000 pages | 3,000,000 pages |
Server Processing Burden
Please be aware that “Cores” in the context of GlobalCapture may refer to a physical or logical processor. What this means is that at any point in time, GlobalCapture has as many cores as you have licensed to devote purely to image processing. GlobalCapture can be scaled nearly infinitely with the addition of extra engines and cores, but the burden of processing lies on the physical processors. What this means for the server or virtual machine that GlobalCapture is housed on is GlobalCapture will indiscriminately use up to 100% of it's allotted cores, with no regard for the other applications or processes running on the server. This should be kept in mind when designing or scoping out an environment. Additional cores in excess of the cores allocated to GlobalCapture may be suggested to maintain system stability of the capture server.