# Limitations of 1search

The following are some of the limitations of the 1search engine which should be taken into consideration when configuring or expanding 1search.

  • Max Processing Time: There is a max processing time of 1 second for each query in order to ensure fair use. For example, if a very large request came through the max time it will run for is 1 second.

    • HTTP Error 422: This is the error that will appear if a request has taken too long to process.
  • Max Uncompressed Payload: There is a max uncompressed payload size of 50MB to ensure that your instance won't fail fair use and can't be used to take up all the space.

    • HTTP Error 413: This error occurs if the max payload size is exceeded.
  • Maximum Indexing Speed: There is a maximum speed of 25 index changes per CPU per second. If this limit is exceeded, pending index changes will remain in a queue for up to 24 hours, if it is not completed in that 24 hours it will be dropped and not indexed, resulting in undefined behavior. -HTTP Error 429: This error occurs if there is a spike in usage which overflows the surge queue. Meaning that CPU usage was already at 100% and there wasn't enough time to scale it up before the spike.

  • Maximum Upload: There is a maximum size upload allowed to the web storage endpoint of 1MB per request, however, multipart uploads can be used as a workaround to this limitation

    • HTTP Error 413: This error occurs if the max upload size is exceeded.
  • In-Memory Search Engine: 1search is an in-memory search engine, if your instance exceeds memory limitations that have been set up, all insert and update requests will be disabled. Clients can view and change the instance type set up for the search engine in the infra section of the client portal. if memory is exceeded, they may have to change the instance to one with a larger memory.

    • HTTP Error 507: This error occurs if your system has exceeded the setup memory buffer for it.
  • Storage Endpoint Errors: The storage endpoint can sometimes respond with errors that clients will have to retry until it works.

    • The Following are the Error Codes Clients Must Retry On
    • [408, 502, 503, 504]
    • These errors are errors the user needs to retry on, and they should continue to retry until it works.