1) We noticed that one the documents that we uploaded for OCR, took about 9 minutes (excluding the upload and download times). When we re-ran the test with the same document, the result came back in 6 seconds this time. Do results of OCR get cached on the server side? If yes, does Abbyy reduce the # of available pages in my account for such requests? If there is no caching, why is there so much discrepancy in response times for the same document? We even observed that the server status to be a constant 103% during this test - so why so much variation if there is no cached results?
2) Let's say, I upload 500 documents to Abbyy Cloud, which are very similar in structure to the test document that took about 9 minutes. What would be the ball park estimate for how much time it could take Abbyy to process such a load? Let's assume that there is no one else on the server submitting a lot of tasks, the server load is constant and we send these 500 requests in parallel. In such a scenario, given that this sample document took 9 minutes at 105% server load, could you please give us a rough estimate on what to expect w.r.t overall processing time? Consider your infrastructure, your VM spin up times on Azure during auto scale, and give us this number.
3) Would it be possible for Abbyy to allocate more resources for faster dedicated processing on our documents, if we give you a 24/48 hour notice that we expect more documents? Can we may be negotiate for on-demand performance lines at a workable pricing model that is mutually beneficially?