FAQ
What is the processing time for 1 OkayDoc landmark checking request?
It’s 1s as the server-side processing time. Processing time differs by OkayDoc module, and image resolution size of the input. Some modules (e.g. microprint) can take up to 8s server-side processing time / request.
What other factors can contribute to the total response time of 1 OkayDoc landmark checking (similarly, other modules too) request?
i) image upload time from client-side to your web and application server, and subsequently transfer time over-the-internet to OkayDoc Cloud, and the API response size in the order described. ii) number of concurrent requests you are sending to OkayDoc Cloud
What is the committed SLA of Innov8tif’s OkayDoc API in production (multi-tenancy Cloud) to clients?
In our License and Support Subscription agreement, SLA is committed as: i) less than 1 minute per API response ** As an equivalent-in-scale comparison, credit bureau’s credit report request and AML risk screening database are usually committed within 2 minutes response time. ii) each client is expected to experience not more than 1 client onboarding request in 1 minute
What is Innov8tif’s policy in load testing?
Innov8tif does not support load testing in our multi-tenancy Cloud. When such need is required, it has to be pre-scheduled with Innov8tif
Can Innov8tif support clients who require concurrency higher than what Innov8tif committed in standard SLA?
Yes. It can be discussed with our commercial team, based on commitment made by client. In fact we do have clients in our multi-tenancy Cloud who committed commercial for more than 1 onboardin request in a minute.
Last updated