Documentation Index
Fetch the complete documentation index at: https://docs.abbyy.com/llms.txt
Use this file to discover all available pages before exploring further.
The ABBYY Vantage cloud service processes thousands of documents per hour and scales up automatically when load increases.
For performance guidance on on-premises installations and Private Cloud, see the Private Cloud Performance Guide. System Processing Capacity
Approximate sustained throughput without noticeable delays in system response:
| Window | Max pages |
|---|
| Per minute (short peaks) | 500 |
| Per hour (short peaks) | 12,500 |
| Per day (8-hour workday) | 50,000 |
Scaling Principles
Microservices, Not Skills
Vantage skills are workflows made up of activities — such as OCR, classification, and extraction (you can see activities when editing a skill). Each activity is performed by a dedicated pool of microservices.
Scaling happens at the microservice level. The system monitors the queue of tasks and the available microservices for each activity. If a queue starts growing, more microservices are added for that activity.
Because scaling doesn’t happen at the skill level, higher load on one skill doesn’t affect the performance of other skills — as long as total processing stays within the limits above. For the same reason, you can’t increase performance by duplicating a skill and splitting the document flow in two, except in specific cases where the bottleneck is an SFTP or mail folder used for uploading documents.
Across the System, Not Per Tenant
Resources scale system-wide, so each tenant draws from a larger shared pool. When an overload happens, the system takes about five minutes to scale up. While new agents are starting, resources are distributed so that no single tenant has a significant proportion of their transactions hanging. Once scaling completes, processing speed returns to its baseline or slightly above. On rare occasions, processing times may increase by up to 30%.
Protection Against Emergency Overloads
A built-in limit prevents system overuse — for example, from a programming error on the client side. If a tenant persistently overloads the system, Vantage caps that tenant’s resources at the usual processing capacity and queues excess transactions.
Slowdowns, if they occur, show up on the service health status page.
API Calls and Scaling
When submitting files via the Vantage API, make as many calls as you need. If the system starts scaling up, all transactions are still created — some may be queued until capacity increases. Vantage has built-in DDoS protection that doesn’t interfere with regular file upload requests.
Uploading Files from an SFTP or Mail Folder
The SFTP storage has hundreds of terabytes of space. The agent that submits files for processing via the Vantage API checks your SFTP folder every 20 seconds and picks up a maximum of 30 files at a time. If SFTP upload becomes a bottleneck, consider creating two skills, each with its own SFTP folder — this lets two agents pick up files simultaneously.
The mail folder import agent collects up to 50 emails every minute and creates a transaction for each message body and attachment. If mail folder import becomes a bottleneck, the same split-into-two-skills workaround applies.