[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8},"actionData","errors","root",{"_11":-5},"routes/user.$name.collections",{"_9":10,"_11":12,"_13":14,"_15":16,"_17":18,"_19":16},"topics",[36],"user",{"_20":21,"_13":14,"_22":23,"_24":25,"_26":27,"_28":29,"_30":31,"_32":33,"_34":35},"loginname","liuzhaohui","page",1,"limit",20,"total","id","2314","avatar_url","http://www.gravatar.com/avatar/03d8dc08355d4f345d8921bfd0d348dd?size=48","githubUsername","","create_at","2012-02-02 01:39:14.401","score",25,"topic_count",0,"reply_count",5,"is_star",false,{"_20":37,"_38":39,"_40":-5,"_41":42,"_43":44,"_45":46,"_47":35,"_48":35,"_32":49,"_50":51,"_26":52,"_53":54},"177","author_id","7","tab","content","

还在为node运行于单进程而苦恼么？即便是node本身提供了cluster功能，或者在github和npm上有很多优秀的模块帮你做封装，但你仍然逃避不掉这些问题：

\n\n

性能问题；
多进程worker的存活状态管理；
服务的平滑重启；
配置或者静态数据的动态reload.

\n\n

我相信你完全有能力把这些事情做得很好。但在自己动手之前，为何不尝试一下node-cluster呢？\nhttps://github.com/aleafs/node-cluster

\n\n

node-cluster只有一个文件，区区500多行代码（包括注释），为你解决了上面的所有问题。利用node-cluster构建你的多进程服务非常简单：

\n\n

在master进程中，你只需要5行代码：

\n\n

var cluster = require('node-cluster');\n\nvar master = new cluster.Master();\nmaster.register(8080, 'app.js');\nmaster.dispatch();\n

在worker进程中，你只需要关心你的app逻辑即可。一个基于HTTP协议的典型例子如下：

\n\n

var Http  = require('http');\nvar cluster = require('node-cluster');\n\nvar admin  = new cluster.Worker();\nvar server  = Http.createServer(function (req, res) {\n  admin.transact();\n\n  res.writeHead(200, {'Content-Type': 'text/plain;charset=utf-8'});\n  res.end('hello world');\n\n  admin.release();\n});\n\nadmin.ready(function (socket) {\n  server.emit('connection', socket);\n});\n

\n\n

实际上，我设计node-cluster的初衷可不只是这点用途。糯米们都能发掘出哪些应用场景呢？

","title","master + worker模式的node多核解决框架——node-cluster","last_reply_at","2016-05-05 12:13:41.429","good","top",27,"visit_count",27871,"2012-02-01 13:13:53.582","author",{"_13":55,"_22":56},"pengchun","http://www.gravatar.com/avatar/30a95610615ba601ff60c740fa010975?s=48"]