Most of these scripts are already installed, a few are from the new DTrace book. In this post, I’ll cover the top ten Mac OS X DTrace scripts that I use for figuring out why laptops are slow or why applications are misbehaving. DTrace, however, can see (just about) everything. Standard performance analysis tools like Activity Monitor and top(1) (and any third-party tools based on the same foundation) can’t tell you some key information about activity on your system, such as how much CPU consumption is caused by short-lived processes, or which processes are causing disk I/O. Applications can become slow or unresponsive while waiting for CPU work, memory requests or disk I/O to complete.įor people who try to ignore the slowdown, the question can become: I work in an office where everyone has MacBook Pros, and “why is my MacBook slow?” is a common question. I use them regularly to answer this question: I’m familiar with the latter as I wrote the originals for the DTraceToolkit, which Apple then customized and enhanced for Mac OS X where they are shipped by default (great!). It provides data for Apple’s Instruments tool, as well as a collection of command line tools that are implemented as DTrace scripts. Since version 10.5 “Leopard”, Mac OS X has had DTrace, a tool used for performance analysis and troubleshooting.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |