Jump to content

Top Processes Based Memory or CPU Usage Workflow


Recommended Posts


Alfred 2 Top Process Workflow

 
The initial motive of this workflow is to avoid frequent visits to the Activity Monitor when the fan goes loud. Now it has been evolved with two major features:
 
Suggestions are welcome. And Please go to http://zhaocai.github.com/alfred2-top-workflow/ for better view of the installation instruction.
 
- 1) List/Kill Top Processes by Memory/CPU/IO Usage
 
mixed%20top%20processes.png
 
 
- 2) (working in progress) Get a glance of system status including internal battery, fan speed, CPU/GPU Temperature, bluetooth battery, disk capacity, etc.
 
glance.png
 
Usage
 
0. Show Help
 
Just type -?, -h, or --help after the keyword to show help.
 
help.png
 
1. Top Processes
 
A. Keywords:
 
1.) top: Show a mixed processes list based on top cpu/memory usage.
 
 
     1. top -m, top --memory to show processes ranked by memory usage
 
     2. top -c, top --cpu, to show processes ranked by cpu usage
 
     3. top -i, top --io, to show processes ranked by io usage with callback from top io trace collector.
 
   Top IO requires [DTrace][Dtrace] and it would take a while to finish. The new callback design is to run the job in he background and post a notification (OSX 10.8+) using notification center. Click on the notification to show the result in alfred.
 
callback.png
 
 
 
 
Modifier Key
 
   - none    : The default action is to list files opened by process ID
   - control : Kill the selected process
   - command : kill forcefully (kill -9)
   - alt     : Nice (lower) the selected process's cpu priority
   - shift   : Search web for process information
 
 
2.) kill: Filter process to kill.
 
Modifier Key
 
   - none: The default action is to kill by process ID
   - command : kill forcefully (kill -9)
 
3.) lsof: List files opened by process id
 
Modifier Key
 
   - none: The default action is to reveal file in Finder
 
B. Filter by Query
 
1.) To search for process state, use :idle, :sleep, :stopped, :zombie, :uninterruptible, :runnable, etc.
 
top%20sleep.png
 
 
2. Glance an Eye on your system
 
#### A. Keywords:
 
  • glance: Show system information including internal battery, bluetooth battery, disk capacity, etc.
 
 
battery.png
 
B. Change Display Order
 
  • Activate Alfred PreferencesAdvancedTop Result Keyword Latching
 
 
Alfred_Preferences_Learning.png
 
  • Hit Enter for the feedback item you wish to show up on the top.
 
 
Installation

Two ways are provided:

  1. You can download the Top Processes.alfredworkflow and import to Alfred 2. This method is suitable forregular users.

  2. You can git clone or fork this repository and use rake install and rake uninstall to install. Check rake -T for available tasks. This method create a symlink to the alfred workflow directory: "~/Library/Application Support/Alfred 2/Alfred.alfredpreferences/workflows". This method is suitable fordevelopers.

 
 
Troubleshooting
 
1. Does not work in Mac OSX 10.9 (Maverick)
 
In OSX 10.9, the system ruby is upgraded to 2.0.0. You need to download the new version of this workflow which packs the ruby gems for 2.0.0 inside.
 
If the downloaded version does not work, try 
 
1.) open Terminal.app. If you use rvm or rbenv, switch to the system ruby.
  • run cd "$HOME/Library/Application Support/Alfred 2/Alfred.alfredpreferences/workflows/me.zhaowu.top" && rake bundle:update
 
2. iotop causes mouse lagging
 
This issue is not caused by this workflow but by [DTrace][DTrace]. The related system log message is IOHIDSystem cursor update overdue. Resending..
In my Macbook Pro, any [DTrace][DTrace] based program will introduce this issue including the mac built-in /usr/bin/iotop, and /Applications/Xcode.app/Contents/Applications/Instruments.app .
 
I upgrade to OS X 10.9 and this issue is resolved.
 
3. Encoding::CompatibilityError: incompatible character encodings: ASCII-8BIT and UTF-8
 
Add the following contents to /etc/launchd.conf. Restart is required.
 
setenv LANG en_US.UTF-8
setenv LC_ALL en_US.UTF-8
 
 

 

Edited by zhaowu
Link to comment

Interesting.  One question on the workflow, what exactly does the cmd modifier do?  

 

Press and hold cmd and the highlighted items info changes to 'Force Kill'.  

If I continue to hold down cmd and either click on the selected item or hit the return key it will kill the app.  

If I don't press the cmd key and either mouse click or hit return on an item it will also kill the app.  

Link to comment

Normally, kill a process means to send a signal to the process and let it finish it up and quit. It is safe. 

 

Force Kill means to send '-9       KILL (non-catchable, non-ignorable kill)' signal to kill the process. Normal it is not recommended to do that unless the process is hung or not responding. You may lose data by this.

 

Interesting.  One question on the workflow, what exactly does the cmd modifier do?  

 

Press and hold cmd and the highlighted items info changes to 'Force Kill'.  

If I continue to hold down cmd and either click on the selected item or hit the return key it will kill the app.  

If I don't press the cmd key and either mouse click or hit return on an item it will also kill the app.  

Link to comment

Update: (March 25, 2013)
- add `lsof` keyword to List Files Opened by Process ID as default action
- now you can search for process state like idle, sleep, stopped, zombie, uninterruptible, runnable, etc.

- add kill keyword which would be a replacement for similar workflow

Edited by zhaowu
Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...