API 的基准测试/性能测试 - REST/SOAP
我正在尝试在工作中对 API 进行基准测试/性能测试。所以面向客户端的是REST格式，而后端数据是通过SOAP消息检索的。所以我的问题是，你们中的一些人能否分享一下你们如何实现它的想法（如果你们过去这样做过/现在这样做过），我基本上对 API 为客户端返回结果所需的平均响应时间感兴趣，
请让我知道您是否需要任何其他信息来回答这个问题
I'm trying to benchmark/ do performance testing of API's at my work. So the client facing is REST format while the backend data is retrieved by SOAP messages. So my question is can some of you share your thoughts on how you implement it (if you have done so in the past/doing it now), am basically interested in avg response time it takes for API to return results for the client
Please let me know if you need any additional information to answer the question
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
真的不能比马克说得更好：http://www.mnot.net/blog/2011 /05/18/http_benchmark_rules
Could not say it any better than Mark, really: http://www.mnot.net/blog/2011/05/18/http_benchmark_rules
也许你应该尝试一下 JMeter。
Maybe you should give JMeter a try.
Jmeter 为您提供额外的灵活性，例如添加功能案例以及性能详细信息。结果几乎与 Apache Benchmark 工具类似。
提供功能测试结果、性能计数器设置、呼叫响应时间详细信息、CPU 和内存变化以及负载/压力结果以及不同带宽和浏览器设置的详细信息 - Visual Studio Team 系统
我使用
VSTS2010进行性能测试。 GET 和 POST 也很简单。 PUT 和 DELETE 需要webtest的编码版本。谢谢，
马杜苏达南
乐购
Jmeter gives you additional flexibility like adding functional cases along with performance details. Results will be almost similar to Apache Benchmark tool.
The detailed one which gives Functional Test Result, performance counters settings, Call response time details, CPU and Memory changes along with Load/Stress results, with different bandwidth and browser settings - Visual Studio Team system
I used
VSTS2010for performance testing. Also GET and POST are straight forward. PUT and DELETE need coded version ofwebtest.Thanks,
Madhusudanan
Tesco
如果您正在尝试测试 REST -> SOAP 调用。您可以考虑的另一件事是创建一些存根（用于后端）。这样你就可以执行测试 REST -> Stub 性能随后 Stub ->肥皂性能。这将有助于分析各个组件。
If you are trying to test the REST -> SOAP calls. One more thing you can consider is to have some stubs created (for backend). This way you can perf test REST -> Stub performance followed by Stub -> SOAP perfomance. This will help in analyzing the individual components.