node club的并发性能很低嘛
发布于 11 年前 作者 zhengweisk 5468 次浏览 最后一次编辑是 8 年前

node club的并发性能很低嘛 [root@web nodeclub]# ab -c 100 -t 10 http://184.173.236.100:3000/topic/51e8af1c071176d52b0001d3 This is ApacheBench, Version 2.3 <$Revision: 655654 $> Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/ Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking 184.173.236.100 (be patient) Finished 566 requests

Server Software:
Server Hostname: 184.173.236.100 Server Port: 3000

Document Path: /topic/51e8af1c071176d52b0001d3 Document Length: 6707 bytes

Concurrency Level: 100 Time taken for tests: 10.001 seconds Complete requests: 566 Failed requests: 0 Write errors: 0 Total transferred: 3973622 bytes HTML transferred: 3796162 bytes Requests per second: 56.59 [#/sec] (mean) Time per request: 1766.964 [ms] (mean) Time per request: 17.670 [ms] (mean, across all concurrent requests) Transfer rate: 388.01 [Kbytes/sec] received

Connection Times (ms) min mean[+/-sd] median max Connect: 0 0 0.7 0 2 Processing: 742 1619 292.8 1640 2455 Waiting: 742 1619 292.8 1640 2455 Total: 743 1619 292.5 1640 2455

Percentage of the requests served within a certain time (ms) 50% 1640 66% 1760 75% 1817 80% 1861 90% 1962 95% 2074 98% 2205 99% 2254 100% 2455 (longest request)

5 回复

求推荐个给力的…

这个并发太低了。

可能是服务器不行

把 HTML 渲染移到前端对 CNode 可行不?

node club肯定是没办法有很高的并发的。 没有缓存且只用了单进程。

但是LZ的测试时间只有10S,太短,需要更长时间测试且分析一下CPU和内存、网络,哪个是瓶颈。

回到顶部