2 Replies Latest reply on Apr 7, 2017 2:13 AM by anna RSS
    qzhang Newbie

    How does TW instance behave when lots of twApi_InvokeService request from edge is launched simultaneously.

    hello developers,

    We have lots of edges running agent developed from C sdk, the agent will using twApi_InvokeService api to update the corresponding Thing model on Platform.

    We have experienced a trouble that the platform seems out of resource to handle all the invoke service request from the edges issued simultaneously.

    The symptoms is:

    1. TW instance is responsive to the simple service invoke request slowly(like invoking Thing.getAvatarUrl), almost more than 1 minute), 

    2. after we shutdown all the edges, the platform seems still process the accumulated service invoking from the edges.

    So my questions are:

    1 How does TW instance behave when lots of service invoking request from edge is launched simultaneously, will they be queued and be processed in sequence? If the service invoking request is queueing, will this behavior lead to memory overload at the end?

    2 If the service invoking request is achieving on the platform, what will happened when the edge is shut down, will the platform cancel the queueing service invoking request?

    3 At the edge side,  will the parameters "timeout" and "forceConnect" impact the queueing behavior?

    I'm really looking forward to your answers.