HC2 API - what else uses it ?

[AutoFrank 372]

Hi all,

I am looking to build out my understanding of the HC2 Rest API. Specifically its capacity to execute a lot of calls (as opposed to what functions are available) and what else leverages the API and battles for capacity.

I have two reasons for posting the topic - (a) I may be having an issue and am trying to debug and (b) increasing my systems knowledge.

 

My understand is that the API is used the following...

1. If an http request is made to the HC2 from an external system
2. If a http request is made from a browser to the HC2

 

.. but is it used for ...

The android app I run on my tablets/phones ( yes ?  )

The iOS app running on some ipads/phones ( yes ?  )

If the HC2 scene makes a http request to an external system ( assume no ? )

Does the HC2 FW itself leverage the API in anyway ( assume not ?)

If a scene executes a http request to localhost / 127.0.0.1 (assume yes ?)

.. what else uses it ?

 

now if I send a lot of API calls..

What would people expect to be a resonable number before thresholds are hit (100 per second, 400 per second, 1000 per second ?)

        ----- assuming the are basic calls, (ie return a sensor state, true-false, return, global variable value,etc

What starts to happen to system resources ?

       ---- Do I start to run out of memory

      ----- Do I see my CPU utilisation start to peak close to 100%

     ------ or does the system stay stable and the eveything start to slow down ?

 

Thanks

Frank