blocks|key|361762|text|JMeter在这方面做得很好。您可以录制您的会话，并根据自己的喜好进行调整。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|361763|所谓的“ajax负载测试”在这个网站上是一个反复出现的话题，经常被混淆。因此，让我们直截了当地说:负载测试一个普通的网页和使用ajax进行负载测试并没有什么区别。这一切都归结为离散的请求；它们只是碰巧不是完整的页面刷新。|361764|要记住的一件事是，负载测试处理请求的服务器(负载测试)和正在更新的UI组件在屏幕上的性能(+javascript的执行情况)之间有明显的区别。|361765|简单的负载测试示例：|361766|361767|initial+page+load|ordered-list-item|361768|登录|361769|navigate?|361770|5-10+'ajax‘请求(或任何适合您的应用程序用法的请求|361771|361772|entityMap|0|LINK|mutability|MUTABLE|url|http://jakarta.apache.org/jmeter/^0|0|6|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]]|C|$]]|$1|D|3|E|5|6|7|16|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|17|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|18|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|19|8|@]|9|@]|C|$]]|$1|K|3|L|5|M|7|1A|8|@]|9|@]|C|$]]|$1|N|3|O|5|M|7|1B|8|@]|9|@]|C|$]]|$1|P|3|Q|5|M|7|1C|8|@]|9|@]|C|$]]|$1|R|3|S|5|M|7|1D|8|@]|9|@]|C|$]]|$1|T|3|-4|5|6|7|1E|8|@]|9|@]|C|$]]|$1|U|3|-4|5|6|7|1F|8|@]|9|@]|C|$]]]|V|$W|$5|X|Y|Z|C|$10|11]]]]

<a href="http://jakarta.apache.org/jmeter/" rel="nofollow noreferrer">JMeter</a> is great at this. You may record your sessions and tweak them to your liking. 

So-called 'ajax load testing' is a recurring subject on this site, and is often confused. So let's get it straight: There is really no difference between load testing a normal web page and load testing with ajax. It all boils down to discrete requests; they just happen to not be full page refreshes. 

One thing to keep in mind is there is a distinct difference between load testing the server processing the requests (a load test) and the performance on screen of the UI components being updated (how well your javascript performs.)

Simple load test example:

<ol>
<li>initial page load</li>
<li>login </li>
<li>navigate?</li>
<li>5-10 'ajax' requests (or whatever may fit your application usage pattern)</li>
<li>logout</li>
</ol>

blocks|key|361668|text|有一些负载测试工具可以支持AJAX。例如，WebLoad|type|unstyled|depth|inlineStyleRanges|entityRanges|data|361669|http://www.radview.com/solutions/ajax-load-testing.aspx|offset|length|361670|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1J|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

There are load testing tools that can support AJAX. For example, WebLoad

<a href="http://www.radview.com/solutions/ajax-load-testing.aspx" rel="nofollow noreferrer">http://www.radview.com/solutions/ajax-load-testing.aspx</a>

blocks|key|361694|text|您真正想要的是对服务器处理ajax请求的能力进行压力测试。使用在“记录”测试时查看请求的加载工具，然后进行适当的调优。我只使用了vs测试版，所以我不能给你指出一个低成本的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|361695|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

What you really want is to stress test is the server's ability to handle the ajax requests. Use a load tool that looks at the requests while "recording" the test, and then tune as appropriate. I have only used the vs test edition one, so I can't point you to a low cost one.

blocks|key|3579752|text|我在某种程度上不同意内森和弗雷迪的观点。他们认为"AJAX测试“实际上与HTTP请求没有什么不同，这一点是正确的。但这并不是那么简单。请参阅我在Why+Load+Testing+Ajax+is+Hard上关于Ajaxian.com的文章。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3579753|Pylot和Grinder都是用于生成JMeter请求的优秀工具(我个人推荐Pylot)。但在本质上，它们并不充当浏览器并处理JavaScript，这意味着它们所做的一切只是重播他们在创纪录的时间看到的流量。如果这些AJAX请求对于该会话是唯一的，那么它们可能不适合/不适合于在大容量中重放。|3579754|事实是，随着更多的逻辑被下推到浏览器中，使用传统的负载测试工具正确模拟流量变得更加困难(如果不是不可能的话)。|3579755|在我的文章中，我给出了一个简单的例子，当你想要查询1000个不同的搜索词时，测试像Google主页这样的东西变得多么困难(负载测试期间的一个重要目标)。要使用JMeter/Pylot/Grinder完成这项工作，您实际上需要用该工具的本机语言重新编写AJAX代码的一部分(在本例中是使用jQuery)。|3579756|如果您的目标是测量用户所感知的响应时间(这可以说是一天结束时最重要的事情)，那么事情就会变得更加复杂。对于使用Comet/“反向Ajax”(一种长时间保持开放套接字的技术)的真正复杂的应用程序，传统的加载工具根本不起作用。|3579757|我的公司BrowserMob提供了一个load+testing+service，它使用基于Selenium的火狐浏览器来驱动成百上千个真正的浏览器，允许您测量和计时在浏览器中看到的可视元素的性能。我们还支持传统的虚拟用户(盲HTTP流量)和模拟浏览器(通过HtmlUnit)。|3579758|话虽如此，通常像BrowserMob这样的服务加上传统的负载测试的混合是正确的方法。也就是说，真正的浏览器对于完全逼真的负载测试来说是很棒的，但它们永远不会像“虚拟用户”那样经济，因为它们需要10-100倍的RAM和CPU。关于是否使用simulate+or+not+to+simulate+virtual+users，请参阅我最近的一篇博文。|3579759|希望这能有所帮助！|3579760|entityMap|0|LINK|mutability|MUTABLE|url|http://ajaxian.com/archives/why-load-testing-ajax-is-hard|1|http://browsermob.com/|2|http://seleniumhq.org/|3|http://htmlunit.sourceforge.net/|4|http://blog.browsermob.com/2009/02/virtual-users-to-simulate-or-not-to-simulate/^0|20|T|0|0|0|0|0|0|J|K|1|19|8|2|3K|8|3|0|3A|15|4|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@$A|18|B|19|1|1A]]|C|$]]|$1|D|3|E|5|6|7|1B|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|1C|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|1D|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|1E|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|1F|8|@]|9|@$A|1G|B|1H|1|1I]|$A|1J|B|1K|1|1L]|$A|1M|B|1N|1|1O]]|C|$]]|$1|N|3|O|5|6|7|1P|8|@]|9|@$A|1Q|B|1R|1|1S]]|C|$]]|$1|P|3|Q|5|6|7|1T|8|@]|9|@]|C|$]]|$1|R|3|-4|5|6|7|1U|8|@]|9|@]|C|$]]]|S|$T|$5|U|V|W|C|$X|Y]]|Z|$5|U|V|W|C|$X|10]]|11|$5|U|V|W|C|$X|12]]|13|$5|U|V|W|C|$X|14]]|15|$5|U|V|W|C|$X|16]]]]

I disagree with Nathan and Freddy to some degree. They are correct that "AJAX testing" is really no different in that HTTP requests are made. But it's not that simple. See my article on Ajaxian.com on <a href="http://ajaxian.com/archives/why-load-testing-ajax-is-hard" rel="nofollow noreferrer">Why Load Testing Ajax is Hard</a>.

JMeter, Pylot, and The Grinder are all great tools for generating HTTP requests (I personally recommend Pylot). But at their core, they don't act as a browser and process JavaScript, meaning all they do is replay the traffic they saw at record time. If those AJAX requests were unique to that session, they may not be suitable/correct to replay in large volumes.

The fact is that as more logic is pushed down in to the browser, it becomes much more difficult (if not impossible) to properly simulate the traffic using traditional load testing tools. 

In my article, I give a simple example of how difficult it becomes to test something like Google's home page when you want to query 1000's of different search terms (an important goal during load testing). To do it with JMeter/Pylot/Grinder you effectively end up re-writing parts of the AJAX code (in your case w/ jQuery) over again in the native language of the tool.

It gets even more complex if your goal is to measure the response time as perceived by the user (which is arguably the most important thing at the end of the day). For really complex applications that use Comet/"Reverse Ajax" (a technique that keeps open sockets for long periods of time), traditional load tools don't work at all. 

My company, BrowserMob, provides a <a href="http://browsermob.com" rel="nofollow noreferrer">load testing service</a> that uses Firefox browsers, powered by <a href="http://seleniumhq.org" rel="nofollow noreferrer">Selenium</a>, to drive hundreds or thousands of real browsers, allowing you to measure and time the performance of visual elements as seen in the browser. We also support traditional virtual users (blind HTTP traffic) and a simulated browser (via <a href="http://htmlunit.sourceforge.net/" rel="nofollow noreferrer">HtmlUnit</a>).

All that said, usually a mix of a service like BrowserMob plus traditional load testing is the right approach. That is, real browsers are great for a full-fidelity load test, but they will never be as economical as "virtual users", since they require 10-100X more RAM and CPU. See my recent blog post on whether to <a href="http://blog.browsermob.com/2009/02/virtual-users-to-simulate-or-not-to-simulate/" rel="nofollow noreferrer">simulate or not to simulate virtual users</a>.

Hope that helps!

blocks|key|4426271|text|你可以使用像openSTA这样的东西。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4426272|这允许记录与网站的会话，然后通过相对简单的脚本语言回放。|4426273|您还可以轻松地测试web服务并编写自己的脚本。|4426274|它允许您以任何想要的方式在测试中将脚本放在一起，并配置迭代的数量、每次迭代中的用户数、引入每个新用户的提升时间以及每次迭代之间的延迟。测试也可以安排在未来。|4426275|它是开源的，而且是免费的。|4426276|它可以生成许多报告，可以保存到电子表格中。然后，我们使用数据透视表来轻松地分析和绘制结果。|4426277|entityMap|0|LINK|mutability|MUTABLE|url|http://www.opensta.org/%2522openSTA%2522^0|6|7|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|D|3|E|5|6|7|Z|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|10|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|11|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|12|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|13|8|@]|9|@]|C|$]]|$1|N|3|-4|5|6|7|14|8|@]|9|@]|C|$]]]|O|$P|$5|Q|R|S|C|$T|U]]]]

You could use something like <a href="http://www.opensta.org/&quot;openSTA&quot;" rel="nofollow noreferrer">openSTA</a>.

This allows a session with a web site to be recorded and then played back via a relatively simple script language.

You can also easily test web services and write your own scripts.

It allows you to put scripts together in a test in any way you want and configure the number of iterations, the number of users in each iteration, the ramp up time to introduce each new user and the delay between each iteration. Tests can also be scheduled in the future.

It's open source and free.

It produces a number of reports which can be saved to a spreadsheet. We then use a pivot table to easily analyse and graph the results.

I have been working on a site that makes some pretty big use of AJAX and dynamic JavaScript on the front end and it's time to start stress testing. But how do you properly stress test something that requires clicking several links on the front-end? One way I was able to easily hit every page of the site quickly and repeatedly was to point a Google Mini at it. But that's not going to click links and then navigate Modal windows and things like that.

Edit - I should point out that the site is done in PHP5 and the JavaScript library used is jQuery. Not sure if this would make any difference but felt it might be useful to know.

Load testing the UI

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我一直在开发一个在前端大量使用AJAX和动态JavaScript的网站，现在是时候开始压力测试了。但是，如何正确地对需要在前端单击多个链接的内容进行压力测试呢？有一种方法可以让我轻松快速、反复地点击网站的每个页面，那就是用Google Mini指向它。但这不会让你点击链接然后浏览Modal窗口之类的东西。编辑-我应该指出的是，该网站是在PHP5中完成的，使用的JavaScript库是jQuery。

问对UI进行负载测试
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问对UI进行负载测试EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问对UI进行负载测试
EN