admin管理员组文章数量:1146251
For instance, login user-action. Say User-action 'login' has total of 5 APIs. (One API actually performs the login and rest of the APIs perform some other actions e.g. load home page, load some other meaningful data on that page etc). My question is about the performance statistics report:
- should we focus on individual API level stats (sequential execution) or
- should our performance report focus more on user level actions (how much time the login user-action took, regardless of how much time each API took individually)?
For instance, login user-action. Say User-action 'login' has total of 5 APIs. (One API actually performs the login and rest of the APIs perform some other actions e.g. load home page, load some other meaningful data on that page etc). My question is about the performance statistics report:
- should we focus on individual API level stats (sequential execution) or
- should our performance report focus more on user level actions (how much time the login user-action took, regardless of how much time each API took individually)?
1 Answer
Reset to default 0Well-behaved JMeter test should act exactly like a real user using a real browser.
Real browsers execute AJAX requests using concurrent thread pool so my expectation is that you should mimic what you see in "Waterfall" tab of your browser developer tools, to wit:
- First request to login
- Followed by X concurrent requests which load home page and meaningful data and these requests need to be parallel, not sequential. Take a look at i.e. Parallel Controller which can simulate browser's network footprint in this scenario.
版权声明:本文标题:jmeter - Should we use individual request (API) level performance stats or user-action level? - Stack Overflow 内容由网友自发贡献,该文观点仅代表作者本人, 转载请联系作者并注明出处:http://www.betaflare.com/web/1737224566a1967969.html, 本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容,一经查实,本站将立刻删除。
发表评论