[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8},"actionData","errors","root",{"_11":-5,"_56":57,"_58":59,"_60":61},"routes/user.$name.collections",{"_9":10,"_11":12,"_13":14,"_15":16,"_17":18,"_19":16},"topics",[35],"user",{"_20":21,"_13":14,"_22":23,"_24":25,"_26":27,"_28":29,"_30":16,"_31":32,"_33":34},"loginname","domliang","page",1,"limit",20,"total","id","8575","avatar_url","http://www.gravatar.com/avatar/2ef84e28b4e6ac944c70e7ead849588b?size=48","githubUsername","","create_at","2013-06-25T14:22:35.714Z","score",15,"topic_count","reply_count",2,"is_star",false,{"_20":36,"_37":38,"_39":-5,"_40":41,"_42":43,"_44":45,"_46":47,"_48":34,"_31":29,"_49":50,"_26":51,"_52":53},"4390","author_id","6617","tab","content","原文地址:[Goodbye node-forever,hello PM2](http://devo.ps/blog/2013/06/26/goodbye-node-forever-hello-pm2.html)\r\n译文地址:[告别node-forever,拥抱PM2](http://se77en.cc/2013/06/27/goodbye-node-forever-hello-pm2-translation/)\r\n\r\n![pm2-logo](http://apps.hemca.com/pm2/pres/pm22.png)\r\n\r\ndevo.ps团队对JavaScript的迷恋已经不是什么秘密了;node.js作为服务器端,AngularJS作为客户端,某种程度上说,我们的堆栈是用它建成的.我们构建[静态客户端和RESTful JSON API](http://devo.ps/blog/2013/01/31/farewell-to-regular-web-development-approaches.html)的方法意味着我们跑了很多的node.js,我必须承认尽管node.js的一切都令人敬畏,但当我们在生产环境中运行它时它仍然会让我们感到头疼.相比一些更加成熟的语言,它的工具和最佳实践仍然缺乏(试想一下:监控,日志,错误处理).\r\n\r\n到目前为止,我们仍然依赖漂亮俏皮的[node-forever模块](https://github.com/nodejitsu/forever).它是非常伟大的模块,不过依然缺失一些功能:\r\n\r\n* 有限的监控和日志功能\r\n* 进程管理配置的支持差\r\n* 不支持集群\r\n* 代码库老化(意味着在升级node.js时频繁的失败)\r\n\r\n这就是为什么我们要在过去的几个月里去写[PM2模块](https://github.com/Unitech/pm2).在我们即将发布针对生产环境的正式版之前我们想先让您看一眼.\r\n\r\n###**PM2到底是什么个东西呢?**\r\n\r\n首先第一件事,你需要先通过`npm`来安装它:\r\n\r\n npm install -g pm2\r\n\r\n让我们通过表格来对比下:\r\n\r\n\r\n\r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n

Feature	Forever	PM2
Keep Alive	✔	✔
Coffeescript	✔
Log aggregation		✔
API		✔
Terminal monitoring		✔
Clustering		✔
JSON configuration		✔

\r\n\r\n\r\n现在让我来介绍一点点主要特性...\r\n\r\n###**原生的集群化支持**\r\n\r\nNode v0.6引入了集群特性,允许你在多个Node应用中共享socket.问题在于,它不能在容器外运行而且需要一些额外的配置来处理主进程和子进程.\r\n\r\nPM2原生支持处理这个问题,而且不需要额外的代码:PM2本身作为主进程,然后它将你的代码封装到一个特殊的集群进程里,就像node.js一样,为你的代码文件添加一些全局变量.\r\n\r\n想要启动一个使用所有CPU核心的集群,你只需要键入如下的指令:\r\n\r\n $ pm2 start app.js -i max\r\n\r\n然后:\r\n\r\n $ pm2 list\r\n\r\n然后就会显示类似下面的东西(ASCII UI FTW);\r\n\r\n![pm2-list](http://apps.hemca.com/pm2/pres/pm2-list.png)\r\n\r\n就像你看到的,现在你的应用有多少个进程就取决于你的CPU核心数了\r\n\r\n###**按照termcaps-HTOP(Linux下的系统监控与进程管理软件)的方式管理**\r\n\r\n通过`pm2 list`命令来观察所有运行的进程以及它们的状态已经足够好了.但是怎么来追踪它们的资源消耗呢?别担心,用这个命令:\r\n\r\n $ pm2 monit\r\n\r\n你可以得到进程(以及集群)的CPU的使用率和内存占用.\r\n\r\n![pm2-monit](http://apps.hemca.com/pm2/pres/pm2-monit.png)\r\n\r\n**声明:**[node-usage](https://github.com/arunoda/node-usage)到目前为止还不支持MacOS(随便什么性能要求),不过它在Linux下运行良好.\r\n\r\n现在,让我们来核实一下我们的集群,还有对内存堆栈的垃圾回收,我们假设你已经有一个HTTP基准测试工具(如果没有,你一定要使用[WRK](https://github.com/wg/wrk)):\r\n\r\n $ express bufallo //Create an express app\r\n $ cd bufallo\r\n $ npm install\r\n $ pm2 start app.js -i max\r\n $ wrk -c 100 -d 100 http://localhost:3000/\r\n\r\n在另一个终端,运行监控选项:\r\n\r\n $ pm2 monit\r\n\r\n耶~\r\n\r\n###**实时集中log处理**\r\n\r\n现在你不得不管理多个集群进程:一个爬取数据,一个处理数据,等等...这就意味着大量log,你可以按照老式的方法处理:\r\n\r\n $ tail -f /path/to/log1 /path/to/log2 ...\r\n\r\n但我们想的很周到,我们增加了`logs`功能:\r\n\r\n $ pm2 logs\r\n\r\n\r\n![pm2-logs](http://apps.hemca.com/pm2/pres/pm2-logs.png)\r\n\r\n###**快速恢复**\r\n\r\n现在事情一切顺利,你的进程嗡嗡的运行着,你需要做一次硬重启(hard restart).现在吗?是的,首先,dump掉:\r\n\r\n $ pm2 dump\r\n\r\n然后,你可以从文件中恢复它:\r\n\r\n $ pm2 kill //让我们假设一个PM2停掉了\r\n $ pm2 resurect //我所有的进程又满血满状态复活了\r\n\r\n\r\n###**强健的API**\r\n\r\n比方说,你想要监控所有被PM2管理的进程,而且同时还想监控运行这些进程的机器的状态(甚至希望创建一个Angular应用来调用这些API...):\r\n\r\n $ pm2 web\r\n\r\n打开浏览器输入[http://localhost:9615](http://localhost:9615) ,我嘞个去!\r\n\r\n###**对了,还有很多特性...**\r\n\r\n* 全部测试通过,\r\n* 新一代的`update-rc.d`(`pm2 startup`),当然它还是alpha版,\r\n* 开发模式下更改文件自动重启(`pm2 dev`),也同样还是草稿,\r\n* 自动刷新log,\r\n* 快捷的通过JSON文件管理你的应用,\r\n* 在error log里记录未捕获的异常,\r\n* 记录重启的次数和时间,\r\n* 退出时自动杀死进程.\r\n\r\n##**下一步计划?**\r\n\r\n首先,你可以去[Github上](https://github.com/Unitech/pm2)粉我们(我们喜欢stars).\r\n\r\n我们开发的PM2提供了先进完整的Node进程管理解决方案.我们希望能有更多的人来帮助我们:更多的pull requests.一些还停留在开发路线图上面的功能我们会尽快完成,下面这些就是:\r\n\r\n* 远程管理/状态校验,\r\n* 嵌入式跨进程通信通道(消息总线),\r\n* V8垃圾回收的内存泄漏检查,\r\n* Web界面,\r\n* 监控数据持久化,\r\n* 邮件通知.\r\n\r\n特别感谢[Makara Wang](https://github.com/makara)的观点和工具,还有[Alex Kocharin](https://github.com/rlidwka)提的建议和提交的代码.\r\n\r\n- 在[Twitter](https://twitter.com/intent/tweet?text=[@devo_ps](/user/devo_ps)%20&related=devo_ps&url=http://devo.ps/blog/2013/06/26/goodbye-node-forever-hello-pm2.html)上给我们反馈吧.\r\n- 欢迎在[Hacker News](http://news.ycombinator.com/item?id=5945420)上和我们一起谈论","title","告别node-forever,拥抱PM2[转载]","last_reply_at","2016-05-10T01:50:01.422Z","good",true,"top","visit_count",24054,"2013-07-31T07:48:33.154Z","author",{"_13":54,"_22":55},"se77en","http://www.gravatar.com/avatar/ac91e951c9a08f0209028162d5809b2a?size=48","zones",[105],"tabs",[75,76,77,78,79,80],"publicConfig",{"_62":63,"_64":25,"_65":66},"apiBaseUrl","https://api.cnodejs.org","turnstileSiteKey","build",{"_67":68,"_69":70,"_71":72,"_73":74},"service","cnode-web","version","0.1.0","commit","09940aa1bc0ad3dfe64235540ced544300ba2865","buildTime","2026-08-02T04:10:22Z",{"_20":16,"_82":103,"_84":104,"_86":47,"_87":16,"_89":97},{"_20":32,"_82":101,"_84":102,"_86":47,"_87":32,"_89":97},{"_20":98,"_82":99,"_84":100,"_86":47,"_87":98,"_89":97},{"_20":95,"_82":46,"_84":96,"_86":47,"_87":95,"_89":97},{"_20":91,"_82":92,"_84":93,"_86":34,"_87":94,"_89":90},{"_20":81,"_82":83,"_84":85,"_86":34,"_87":88,"_89":90},10,"key","test","label","测试","visible","sort_order",91,"scope","admin",9,"dev","开发",90,4,"精华","public",3,"job","招聘","ask","问答","share","分享",{"_20":16,"_106":107,"_108":100,"_109":110,"_111":112,"_86":47,"_87":16},"slug","jobs","name","description","Node.js 招聘信息专区","icon","briefcase"]