For an application that reads data from a file, find the data in the ARC.
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.
In this post, I'll create a ZFS pool, add a file to the pool, destroy the pool, and then recover the file. To do this, I'll use a modified mdb, and a tool I wrote to uncompress ZFS compressed data/metadata (zuncompress).
This post answers a question I occasionally have when I am DTracing code: "How do I trace a function but only if it is called from a specific other function?"
Mr. Max Bruning answers questions regarding memory capping on SmartOS.
Here's an example of using kmem\_flags for debugging kernel memory allocator problems.
Max looks back at his presentation at NodeConf 2013 during which he explained the uses and application of DTrace.
In this blog post, I set up a "dummy" service so that people can see how simple documentation for SMF can be.
Here's an overview of how to debug Node.js applications using DTrace.
Max shares his recent talk about using DTrace to do debugging.
I'm often asked, "I have a process that sometimes exits. Why it is exiting?" This post explains the two reasons behind why processes exit.
Here's more information about how ipdadm(1M), the internet packet disturber, works.
What kind of training does Joyent offer, and why is it different from corporate training found elsewhere?
Why would you want to use SmartMachines or SmartOS as opposed to Linux?
Details of prstat(1M) output, and how it can be useful.