Is the Nx Cloud up? Visit our Status Page for the current health and performance of the Nx Cloud.

Status Page

rate limit of nx cloud and relay

Answered

Comments

8 comments

  • Ichiro
    • Network Optix team

    Hi Karen,

    Thanks for your question. What rate do you mean?

    0
  • Karen Zhang

    Hi Ichiro, 

    Like the max. api request number every minute to each system or the cloud account global.  

    0
  • Ichiro
    • Network Optix team

    Hi Karen,

    As far as I know, there is no specific limit to the request at the moment, however, we do have the same limitation since Nx Witness 3.x, the TCP session of a mediaserver will be 2000 in total, including all the streaming/requests/connections from Nx Clients.

    Can you let us know the appox. rate you may have and the scal/size of the site?

    Thanks.

    0
  • Karen Zhang

    Hi Ichiro, 

    Good to know it. 

    Currently still at system design status, for cloud user-system token http requests, it might have max. 200+ requests in a minute.  

    And for every system, it might have 10+ requests every minute. 

     

    0
  • Ichiro
    • Network Optix team

    Hi Karen,

    Can you elaborate what do you mean by “for cloud user-system token http requests”?
    What is the exact behavior and goal/use case you may want to achieve?

    0
  • Karen Zhang

    Hi Ichiro, 

    200+ requests including getting all of system's(100+) disk/server/camera online information from cloud relay. 

    0
  • Ichiro
    • Network Optix team

    Hi Karen,

    This traffic pattern should generally be fine, but it depends on the type of API requests.
    If the requests are simple and the network is stable, 200-300 requests per minute should not be a problem.

    However, heavy requests (for example, searching in a large analytics database, or your case, like full system info in every request) may take more time and can create a queue.

    Also, if requests need data from multiple servers, the performance will depend on the connection between servers to server. If the connection is unstable, responses may be slower or incomplete.

    For heavier or distributed requests, performance may vary. As we don't really know the site size and scale, so this is the best answer we can provide, you may need to confirm and test on the real environment.

    1
  • Karen Zhang

    Hi Ichiro, 

    Thanks for the info, it helps a lot. 

    0

Please sign in to leave a comment.