用nGrinder和jmeter测试同一https场景,tps和响应时间差别很大

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

用nGrinder和jmeter测试同一https场景,tps和响应时间差别很大

taohuang
This post was updated on .
jmeter和nGrinder agent在同一台服务器,被测接口部署在同一台服务器。

单接口,脚本逻辑流程为读keystore.jks文件,调用gruava.jar计算时间戳签名,发起https post请求。

50线程,jmeter数值为800+,nGrinder tps为140+,原因是什么?






服务器性能无瓶颈
Reply | Threaded
Open this post in threaded view
|

Re: 用nGrinder和jmeter测试同一https场景,tps和响应时间差别很大

junoyoon
Administrator
usually this happens due to connection cost.
Each ngrinder test loop, each http request will make a new connection. (it will be very high cost.)
I think Jmeter might reuse previously established connection.
Reply | Threaded
Open this post in threaded view
|

Re: 用nGrinder和jmeter测试同一https场景,tps和响应时间差别很大

taohuang
Thank you junoyoon !
Reply | Threaded
Open this post in threaded view
|

Re: 用nGrinder和jmeter测试同一https场景,tps和响应时间差别很大

terry
In reply to this post by junoyoon
为什么不用grinder3.11呢?3.11好像解决了这个问题。