TJ Fontaine has been effectively leading Node.js for some time now, so we’re making it official. TJ is exactly the leader who can help take Node.js to 1.0 and beyond.
Joyent is happy to announce that our two Node.js support offerings are available starting today.
Looking back at the blog posts for 2013, I like the range of topics that we write about.
Last week at Node Summit 2013, we were treated to an exhibition of sparkling systems showmanship by Joyent SVP Engineering Bryan Cantrill.
Joyent is pleased to announce Node.js support on just about any OS and infrastructure. Called Node.js Core Support, this new offering from the corporate stewards of Node.js, offers commercial support to the growing number of Node.js users and enterprises outside of Joyent's public or private cloud.
In this blog post, I will show ways to gather information about node.js processes running on SmartOS. Specifically, we'll examine cpu utilization, memory usage, file system I/O, and network I/O.
A few weeks ago Eran Hammer of Wal-Mart labs came to the Node.js core team complaining of a memory leak he had been tracking down for months.
Only a handful of ustack helpers have ever been written: Node, Java, Python, and PHP (the last of which is believed lost to the sands of time), so this post is mainly for a narrow audience of developers, plus anyone who's interested in how this all works.
Node Knockout 2013's competition phase concluded on Sunday night exactly 48 hours after it kicked off at Joyent's headquarters in San Francisco.
As a result of using Node.js at every turn, we have accumulated years of institutional knowledge,opinions, modules, and tools that enable us to run Node.js at scale in production.
To find a performance regression between Node v0.10 and v0.11, I used Joyent Manta instead of git-bisect to find the offending commit(s) among all 550 commits of our development branch in under 4 minutes.
Node.js has some built-in DTrace probes for looking at HTTP request start/done and GC start/done, and I wrote [nhttpsnoop] to report latency based on these probes.
Last week I debugged a Node issue where under some conditions, fork() failure could result in some file descriptors being closed, leading shortly to bedlam. In the best cases, the program would immediately crash, but often it would just do the wrong thing. This happens a lot, of course, and in many ways it's worse than a crash because you have no core dump nor even a stack trace to go on.
The nodeconfeu conference in beautiful Waterford, Ireland was, like nodedublin last year, an excellent chance to learn about all things node.js. I want to thank Cian O'Maidin (and staff) once again for another great conference. Hopefully, I'll be back next year.
This post is the one of several about how we operate Node.js in production at Joyent.