Errors observed - Load test - Flogo App (Rest Trigger to Rest Activity)

[ykalidin]

Performed Load test on Flogo App with simple Rest Trigger and Rest Activity. Below are the steps: 1)Install go-wrk go get github.com/tsliwowicz/go-wrk 2)create the app with latest.json(project-flogo) and run the app(Attached the file). 3)Run the local backend node1.js server.(Used node server to reduce network latency) node node1.js 4)Now run the below command to hit the gateway with 5 concurrent clients: go-wrk -c 5 -d 120 http://localhost:9096/test

The below errors are seen: dial tcp 127.0.0.1:1234 : connect: cannot assign requested address

Also, when using the old TIBCOSoftware/flogo-contrib flow and activities no error is seen for 50 concurrent clients. Repeat the above steps with the oldFlogo.json. go-wrk -c 50 -d 120 http://localhost:9096/test

Attached the latest.json, node1.json and oldFlogo.json. attachments.zip

Note: Have already raised this issue in CLI, on Advice we are raising it in core.

[fm-tibco]

Hi, after reviewing this issue, it probably be filed against core or flow. It is not a CLI issue. Regardless, running your test on my Mac (go version go1.11.1 darwin/amd64), I see much better performance and stability under the new code. I get the following running the latest:

276805 requests in 1m57.289766241s, 38.54MB read Requests/sec: 2360.01 Transfer/sec: 336.49KB Avg Req Time: 2.118635ms Fastest Request: 245.498µs Slowest Request: 1.188148321s Number of Errors: 10

And on the old code:

48911 requests in 1m2.028339413s, 6.81MB read Requests/sec: 788.53 Transfer/sec: 112.43KB Avg Req Time: 6.340939ms Fastest Request: 414.594µs Slowest Request: 5.379473003s Number of Errors: 265

[fm-tibco]

The error I get from both is from the load client and not the engines:

An error occured doing request Get http://localhost:9096/test: net/http: timeout awaiting response headers
empty response

[ykalidin]

@fm-tibco I have verified in Mac and Windows with the latest flogo, no issue is reported in Gateway, But in Ubuntu, Gateway gives the above Error log(connect: cannot assign requested address). Hence I feel issue is only in Ubuntu. Let me know if you need any details.

[ykalidin]

Observation: This error dial tcp 127.0.0.1:1234 : connect: cannot assign requested address may occur in Ubuntu when the system setting "cat /proc/sys/net/ipv4/tcp_tw_reuse" value is 0. Changing this value to 2 avoided the above error.