Minecrab is the answer to one developer/gamer's request for painless, personalized and cheap Minecraft server hosting.
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.
For the past few months Aram Hăvărneanu has been doing some amazing work porting Go to SunOS, and we wanted to help out.
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.
Here is an update of ways to sync or move your server's existing log data to the Manta Storage Service.
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.
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.
More sophisticated series of shell scripts that pull the originals, resize, reformat, extract XMP metadata, and use MapReduce to make a file of metadata one-line descriptions.
Our friends from BayLISA came up to San Francisco again the other night. The occasion was the launch of Brendan Gregg's new book, Systems Performance: Enterprise and the Cloud, and we had the first copies hot off the press to raffle off to three lucky attendees.
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.
Simple JPEG resizing on Manta and the speedup compared to my notebook, mjob share, tips on preserving image color, and uploading large data sets.
This post is the one of several about how we operate Node.js in production at Joyent.