1. Language IO
  2. Language IO API Support
  3. Troubleshooting

Articles in this section

API rate limits and load testing

The purpose of this article is to explain the different limits and response times of the Language IO API.

Important: Make sure that your requests stay within the specified limits. If you exceed these limits, you can expect an increase in latency, and a potential degradation in translation quality.

Rate limits

To ensure the availability and stability of Language IO services, the Language IO API works under the following throttling, burst, and rate limits.

What are the different limits?

  • The Throttling limit is the number of requests per second that the Language IO API can handle consistently.
  • The Burst limit is the emergency maximum request capacity of the Language IO API when the throttling limit is temporarily exceeded.
  • The Rate limit is a hard cap on the total number of requests per customer per month.
  Throttling Limit Burst Limit Rate Limit
Production 75 per second 150 200,000 per month

 

Response Times and Character Limits

What are the average, min, max, p99, p95, and p90 latency numbers?

  Average Minimum Maximum p90 p95 p99
translate endpoint 700ms 380ms 1,500ms 880ms 936ms 1,125ms
detect locale endpoint 167ms 132ms 639ms 188ms 217ms 419ms

 

What are the character limits for the detectLocale "text" and translate "sourceContent" fields?

Language IO recommends that requests to these endpoints contain 5,000 or fewer characters.

 

Load Testing the Language IO API

Load testing can impact Language IO services. To ensure consistent performance across our platform, if you wish to perform load tests, you must coordinate with Language IO to plan and execute them.

Important: Load testing must be approved in advance. Otherwise, Language IO reserves the right to deny requests for load testing.

Required lead time: Please contact Language IO at least two weeks in advance to share your intended load testing plans.

Request

To initiating the process, submit a support request with a relevant subject and include the following details:

  • Business group
  • Point(s) of contact
  • Load test plan details, including:
    • Target start and end date, and time (including the timezone)
    • Endpoints
    • Payload
    • Volume
    • Duration

Include any other details that may help Language IO coordinate or provide guidance for testing.

Next steps

Language IO will acknowledge the support request and begin to coordinate the activity.

Language IO may request additional information, propose alternate timeframes, and provide guidance and instruction.

Confirming the load testing plan

Prior to the start of a test, Language IO must agree to and confirm a final load testing plan with you.

Executing the test

You must perform the test exactly according to the testing plan mutually agreed and confirmed. If deviations are required, you must notify Language IO, and continue only after the updated plan is agreed and confirmed by Language IO.

Related articles