为每秒请求骆驼码头基准测试 [英] camel jetty benchmark testing for requests per second
问题描述
我建立一个高负荷的HTTP服务，它会消耗每秒消息十万并将它传递给邮件系统像ActiveMQ的。
I am building a high load http service that will consume thousands of messages per second and pass it to a messaging system like activemq.
目前，我有接受来自HTTP客户端的职位，并返回一个普通的成功输入反应，我可以这样使用Apache AB。
I currently have a rest service (non-camel, non-jetty) that accepts posts from http clients and returns a plain successful respone and i could load test this using apache ab.
我们也在寻找骆驼码头作为输入端点，因为它有ActiveMQ的集成组件，如果需要，是ESB的一部分。之前，我开始建立一个骆驼码头至ActiveMQ的路线，我想测试骆驼码头可支持负载。什么都要我的码头的必经之路样子，
We are also looking at camel-jetty as input endpoint since it has integration components for activemq and be part of an esb if required. Before i start building a camel-jetty to activemq route i want to test the load that camel-jetty can support. What should my jetty only route look like,
我想到的路线
这（码头：HTTP：//0.0.0.0：8085 /测试）.transform（常数（A））;
from("jetty:http://0.0.0.0:8085/test").transform(constant("a"));
和使用Apache AB测试。
我很担心，如果这条线路提供了一个真正的骆驼码头能力，因为改造可能会增加开销。或者岂不。
and use apache ab to test. I am concerned if this route provides a real camel-jetty capacity since transform could add overhead. or would it not.
根据这些测试我计划带或不带骆驼建立HTTP的MQ。
Based on these tests i am planning to build the http-mq with or without camel.
推荐答案
变换API不会增加显著的开销......我只是跑测试对你的基本路线...
the transform API will not add significant overhead...I just ran a test against your basic route...
ab -n 2000 -c 50 http://localhost:8085/test
和得到了以下...
Concurrency Level: 50
Time taken for tests: 0.459 seconds
Complete requests: 2000
Failed requests: 0
Write errors: 0
Non-2xx responses: 2010
Total transferred: 2916510 bytes
HTML transferred: 2566770 bytes
Requests per second: 4353.85 [#/sec] (mean)
Time per request: 11.484 [ms] (mean)
Time per request: 0.230 [ms] (mean, across all concurrent requests)
Transfer rate: 6200.21 [Kbytes/sec] received
这篇关于为每秒请求骆驼码头基准测试的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
