每秒请求的骆驼码头基准测试 [英] 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.

我们还将camel-jetty 视为输入端点，因为它具有activemq 的集成组件，并且在需要时成为esb 的一部分.在我开始构建camel-jetty 到activemq 路由之前，我想测试camel-jetty 可以支持的负载.我的码头唯一路线应该是什么样子，

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,

我在想路线

from("jetty:http://0.0.0.0:8085/test").transform(constant("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屋！