去年的时候,曾经简单对比了一下golang和nodejs的http模块的性能,见:golang与node.js的http对比测试
那时golang还没发布go1,http模块比nodejs差得很远。
go1出来已经有一段时间了,我知道go的http模块性能已经有比较大的提升,但是最近依然见到有人提起去年写的那篇文章,为避免产生对golang的误解,对于go1的最新测试结果如下。
测试是在Ubuntu 12.04 64位系统下进行的:
go的版本:
- qleelulu@nb:~$ go version
- go version go1
nodejs的版本:
- qleelulu@nb:~$ node -v
- v0.8.6
单cpu测试
nodejs是单进程,只使用一个cpu,所以这里golang在代码中需要限制为只使用一个cpu。
go的代码: (注:go代码都是使用 go build xxx.go 编译)
- package main
- import (
- "fmt"
- "log"
- "net/http"
- "runtime"
- )
- func main() {
- // 限制为1个cpu
- runtime.GOMAXPROCS(1)
- http.HandleFunc("/",func(w http.ResponseWriter,r *http.Request) {
- fmt.Fprint(w,"Hello,world.")
- })
- log.Fatal(http.ListenAndServe(":8080", nil))
- }
golang请求结果:
- qleelulu@nb:~/sources/test$ curl -i http:127.0.0.1:8080/
- HTTP/1.1 200 OK
- Date: Sun,12 Aug 2012 07:21:00 GMT
- Transfer-Encoding: chunked
- Content-Type: text/plain; charset=utf-8
- Hello,world.
- qleelulu@nb:~$ ab -c 100 -n 5000 http:127.0.0.1:8080/
- This is ApacheBench,Version 2.3 <$Revision: 655654 $>
- Server Software:
- Server Hostname: 127.0.0.1
- Server Port: 8080
- Document Path: /
- Document Length: 13 bytes
- Concurrency Level: 100
- Time taken for tests: 0.593 seconds
- Complete requests: 5000
- Failed requests: 0
- Write errors: 0
- Total transferred: 550000 bytes
- HTML transferred: 65000 bytes
- Requests per second: 8427.78 [#/sec] (mean)
- Time per request: 11.866 [ms] (mean)
- Time per request: 0.119 [ms] (mean,across all concurrent requests)
- Transfer rate: 905.33 [Kbytes/sec] received
- ...
Requests per second: 8427.78 [#/sec] (mean)
Requests per second: 7980.73 [#/sec] (mean)
Requests per second: 7509.63 [#/sec] (mean)
Requests per second: 8242.47 [#/sec] (mean)
Requests per second: 8898.19 [#/sec] (mean)
golang单cpu的webbench测试结果:
- qleelulu@nb:~$ webbench -t 30 -c 200 http:127.0.0.1:8080/
- Webbench - Simple Web Benchmark 1.5
- Copyright (c) Radim Kolar 1997-2004,GPL Open Source Software.
- Benchmarking: GET http:127.0.0.1:8080/
- 200 clients,running 30 sec.
- Speed=463124 pages/min,849060 bytes/sec.
- Requests: 231562 susceed,128); line-height:1.5!important">0 Failed.
Speed=463124 pages/min,849060 bytes/sec.
Speed=455322 pages/min,834757 bytes/sec.
Speed=461536 pages/min,846149 bytes/sec.
Speed=454798 pages/min,833803 bytes/sec.
Speed=468592 pages/min,859085 bytes/sec.
golang单CPU webbench测试时,CPU使用率如下:
nodejs 单CPU测试代码:
- var http = require('http');
- http.createServer(function (req,res) {
- res.end('Hello,World.');
- }).listen(8080,'127.0.0.1');
- console.log('Server running at http://127.0.0.1:8080/');
nodejs请求结果:
- qleelulu@nb:~/$ curl -i http:45:23 GMT
- Connection: keep-alive
- Transfer-Encoding: chunked
- Hello,World.
- golang请求结果:
- qleelulu@nb:~/sources/test$ curl -i http: nodejs的单cpu ab测试结果:
655654 $> Server Software: Server Hostname: 0.696 seconds Complete requests: 440000 bytes HTML transferred: 7185.91 [#/sec] (mean) Time per request: 13.916 [ms] (mean) Time per request: 0.139 [ms] (mean,128); line-height:1.5!important">617.54 [Kbytes/sec] received
- $ ab -c 127.0.0.1:8080/
- Requests per second: 14391.80 [#/sec] (mean)
- Requests per second: 14307.09 [#/sec] (mean)
- Requests per second: 14285.31 [#/sec] (mean)
- Requests per second: 15182.34 [#/sec] (mean)
- Requests per second: 14020.53 [#/sec] (mean)
- $ webbench -t 127.0.0.1:8080/
- Speed=750418 pages/min,128); line-height:1.5!important">1375982 bytes/sec.
- Speed=750492 pages/min,128); line-height:1.5!important">1375909 bytes/sec.
- Speed=749128 pages/min,128); line-height:1.5!important">1373408 bytes/sec.
- Speed=749720 pages/min,128); line-height:1.5!important">1374486 bytes/sec.
- Speed=753080 pages/min,128); line-height:1.5!important">1380698 bytes/sec.
nodejs测试代码
使用cluster,使用CPU数量减一个CPU
- var cluster = require('cluster');
- var http = require('http');
- var numcpus = require('os').cpus().length;
- if (cluster.isMaster) {
- Fork workers. fock num of cpuS - 1 works
- for (var i = 1; i < numcpus; i++) {
- cluster.fork();
- }
- cluster.on('exit',function(worker,code,signal) {
- console.log('worker ' + worker.process.pid + ' died');
- });
- cluster.on('fork',signal) {
- console.log('worker ' + worker.process.pid + ' is online');
- });
- } else {
- Workers can share any TCP connection
- In this case its a HTTP server
- http.createServer(function(req,res) {
- res.writeHead(200);
- res.end("hello world.");
- }).listen(8080);
- }
多cpu测试结果来看,总体上来说go和nodejs的性能也还是差不多。
但从ab测试的结果来看,go的QPS要比nodejs高一点,
而从webbench测试结果来看,nodejs的QPS要比go高,但是go的bytes/sec又要比nodes高,可能是go的http返回头比nodes要稍微大一点的原因。
多cpu测试时的cpu使用情况和单cpu测试时的情况差不多,
golang对4个cpu的占用率都在70%左右,
而node则是对3个cpu的占用在90%以上,还有一个cpu的占用率则要稍微低点。
从整体来看,golang和nodejs的http模块性能不相上下。 go1的性能还是比较喜人的,加上go语音的简洁,是个不错的选择(目前可能go的一些第三方模块都不是很成熟)。