Maximizing Throughput

At times, you may wish to load a very large batch of records, especially when you first begin using the Identity API. The Identity service will perform well with parallelized uploads within its concurrency limits.

Concurrency Limits

It is recommended that you not exceed 60 concurrent requests.

Tip
The number of concurrent requests includes both uploads and other operations (such as get/match person). It also includes operations that are still processing, so it is best to wait for a request to complete before issuing another request on that same thread.

Above this limit, you will begin to see diminishing returns, where more concurrency actually cause the other requests to respond more slowly. Excessive numbers of concurrent requests will result in a too many requests error.

Estimated Throughput

Based on our experimentation, the concurrency limit will yield an average throughput of approximately 50 uploads/second, or about 4 million records/day.

Note
These values are based on performance testing in a controlled environment, and are not guarantees. Real-world performance may vary depending on other simultaneous operations, the number of records already in the Identity service, and other factors.