JMeter 攻击性

发布于 2025-01-20 03:31:46 字数 578 浏览 4 评论 0 原文

我正在尝试压力测试一个运行ASPNET Core应用程序的IIS。 为此,我设置了一个与100名工人的线程组 在线程组中,我使用循环控制器 在循环控制器中,我使用访问日志采样器,以重播从NCSA格式的日志文件中获得的真实请求。

我很惊讶地看到我每秒仅获得100个吞吐量。 如何检查这是Jmeter的限制还是我的Web应用程序的限制? 我希望Jmeter爆炸我的服务器,并以100%的速度看到目标CPU拍摄。还是我再次增加了100个线程的高价值?

”在此处输入图像说明”

I am trying to stress test a IIS running a AspNet core App.
to do this i setup a Thread Group with 100 workers
In the thread group I use a Loop Controller
in the loop controller I use a Access Log sampler in order to replay real Get requests obtained from NCSA formatted logfile.

I am amazed to see that i obtain as total throughput only 100 request per sec.
how can i check if this is a limitation of jmeter or if this is a limitation of my web App ?
I would expect jmeter to blast my server and see target CPU shoot at 100%. or shall I increas again already high value of 100 threads ?

enter image description here

enter image description here

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

从此见与不见 2025-01-27 03:31:46
  1. 总吞吐量为每秒86个请求
  2. 100用户可能不足以“爆炸”您的IIS实例,我宁愿建议您选择压力测试,即从1个用户开始,并逐渐增加负载,直到吞吐量开始减少或开始发生错误,无论是第一个即将发生。此外,可能是 bettleneck 不是CPU用法,它可能在其他地方,如果配置不正确或效率低下的算法,Web应用程序可能无法完全利用基础OS和硬件资源
  3. 不使用GUI模式进行测试,则仅用于测试开发和调试时,在执行您应该运行Jmeter在命令行非GUI模式中测试
  4. 有464个错误,检查 jmeter.log文件对于任何可疑条目,
  5. 我认为您无法真正重播您的访问日志,它只能用于静态HTML页面(例如静态html页面),如果有身份验证或动态参数,则可能是您的所有请求都在同一登录页面上,您可以尝试使用并检查响应以确保您的测试正在执行应该做的

  1. Total throughput is 86 requests per second
  2. 100 users might be not enough to "blast" your IIS instance, I would rather recommend going for stress test, i.e. start with 1 user and gradually increase the load until throughput starts decreasing or errors start occurring, whatever comes the first. Moreover it might be the case that the bottleneck is not CPU usage, it may be somewhere else, in case of incorrect configuration or inefficient algorithms the web application may not fully utilize underlying OS and hardware resources
  3. Don't use GUI mode for testing, it's only for test development and debugging, when it comes to execution you should be running JMeter tests in command-line non-GUI mode
  4. There are 464 errors, check jmeter.log file for any suspicious entries
  5. I don't think you can really replay your access log, it can be used only for something simple like static HTML pages, if there is authentication or dynamic parameters it might be the case all your requests are hitting the same login page, you can try running your test using View Results Tree listener and inspect the responses to ensure that your test is doing what it's supposed to be doing

enter image description here

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文