performance - Unequal number of requests sent with Gatling -



performance - Unequal number of requests sent with Gatling -

my intent have 2000 virtual users simultaneously nail api 2 different urls, result first url finished requests , sec url finished 168. doing wrong cause sec url publish part of results;

class hammer1 extends simulation { val repeatcount = 2000 val concurrentusers = 100 object post { // repeat loop resolved @ runtime val post = repeat(repeatcount, "i") { // note how forcefulness counter name can reuse exec(http("post") .post("/postdata") .header(httpheadernames.contenttype, httpheadervalues.applicationjson) .queryparam("""size""", "1000") .body(stringbody("""{"payload":"large number of 9s"}""") ) .pause(1) } } object { // repeat loop resolved @ runtime val = repeat(repeatcount, "i") { // note how forcefulness counter name can reuse exec(http("get") .get("/getdata") ) . pause(1) } } val httpconf = http //.baseurl("http://<url>") //.baseurl("http://localhost:10010") . baseurl("http://<url>") val posters = scenario("posters").exec(post.post) val getters = scenario("getters").exec(get.get) setup(posters.inject(rampusers(concurrentusers) on (10 seconds)), getters.inject(rampusers(concurrentusers) on (10 seconds)) ).protocols(httpconf) }

my2cents: content gets served getters expire date header, cached. see caching documentation.

then, please validate answers previous question?

performance gatling

Comments

Popular posts from this blog

c - Compilation of a code: unkown type name string -

java - Bypassing "final local variable defined in an enclosing type" -

json - Hibernate and Jackson (java.lang.IllegalStateException: Cannot call sendError() after the response has been committed) -