Loggly的最大吞吐量是多少？

Question

Loggly处理的每秒客户端请求数量是多少？我每秒只能处理大约10-20个请求,我想知道这是否正常.

Answer 1

我刚刚运行了一堆测试,发现使用syslog-ng通过tcp连接无法真正处理.

以下是我想要试用的测试结果.我使用了balabit的"loggen"程序,并向loggly分配给我的tcp端口发送了200字节的消息.请注意,尽管syslog RFC(至少3164)声明日志消息不应超过1024字节,但我使用200字节数据包只是为了公平,因为许多消息都很小.

注册一个免费帐户.配置TCP连接进行测试.尝试发送各种金额,结果:

测试1:失败

loggen -iS -r 6000  -s 200 -I 100 logs.loggly.com 16225
Send error Broken pipe, results may be skewed.      
average rate = 1392.13 msg/sec, count=18296, time=13.142, (average) msg size=200, bandwidth=271.74 kB/sec

测试2:失败

loggen -iS -r 4000  -s 200 -I 100 logs.loggly.com 16225 
Send error Broken pipe, results may be skewed.       
average rate = 2767.16 msg/sec, count=121146, time=43.779, (average) msg size=200, bandwidth=540.15 kB/sec

测试3:失败

loggen -iS -r 2500  -s 200 -I 100 logs.loggly.com 16225  
Send error Broken pipe, results may be skewed.      
average rate = 1931.27 msg/sec, count=85878, time=44.467, (average) msg size=200, bandwidth=376.98 kB/sec

测试4:失败

loggen -iS -r 2000  -s 200 -I 100 logs.loggly.com 16225    
Send error Broken pipe, results may be skewed.      
average rate = 1617.72 msg/sec, count=83134, time=51.389, (average) msg size=200, bandwidth=315.78 kB/sec

测试5:失败

loggen -iS -r 1000  -s 200 -I 100 logs.loggly.com 16225 
Send error Broken pipe, results may be skewed.      
average rate = 936.50 msg/sec, count=63331, time=67.624, (average) msg size=200, bandwidth=182.81 kB/sec

测试6:配置持续时间PASS,失败> 100秒 - 参见测试7

loggen -iS -r 500  -s 200 -I 100 logs.loggly.com 16225  
average rate = 325.00 msg/sec, count=32501, time=100.001, (average) msg size=200, bandwidth=63.44 kB/sec

测试7:失败 - 更长时间内进行新测试@ 500 EPS并且管道在255秒后损坏:

loggen -iS -r 500  -s 200 -I 10000 logs.loggly.com 16225
Send error Broken pipe, results may be skewed.     
average rate = 323.35 msg/sec, count=82642, time=255.577, (average) msg size=200, bandwidth=63.12 kB/sec

测试8:失败(运行时间更长@ 200 EPS,但仍然失败)

loggen -iS -r 200  -s 200 -I 10000 logs.loggly.com 16225 
Send error Broken pipe, results may be skewed.      
average rate = 163.53 msg/sec, count=234090, time=1431.470, (average) msg size=200, bandwidth=31.92 kB/sec

测试9:失败(再次,运行时间更长但仍然失败)

loggen -iS -r 50  -s 200 -I 10000 logs.loggly.com 16225    
Send error Broken pipe, results may be skewed.    
average rate = 47.36 msg/sec, count=89325, time=1886.014, (average) msg size=200, bandwidth=9.25 kB/sec

测试10:失败？(结果相同,但又失去了联系.很难相信他们无法处理10 eps？)

loggen -iS -r 10  -s 200 -I 10000 logs.loggly.com 16225 
Send error Broken pipe, results may be skewed.  
average rate = 9.94 msg/sec, count=1568, time=157.770, (average) msg size=200, bandwidth=1.94 kB/sec

做了一些网络搜索,看看loggly实际上可以做什么,但是只有营销材料说它是可扩展的,而不是它的可扩展性.我确实找到了这个:http: //twitter.com/jordansissel/status/5948244626509824 这是每秒只有22个事件......

完全披露:我是LogZilla的创始人,因此我正在测试竞争,因为我们正在推出基于云的系统日志解决方案.我的测试表明,我们的软件能够处理每秒2,000到12,000个事件,具体取决于我们在云中使用的服务器.