|
|
Raw numbers
Ok, here's a Unixy way to get some more useful numbers here. If I was thinking a bit more in advance I would have tried this myself, but I didn't so we'll need someone else to try it.
Fire up an instance of the Terminal, and enter the following commands: top -w -l1 > "top_output_`date`.txt" sudo update_prebinding -root / top -w -l1 > "top_output_`date`.txt"
The middle command is the one from the original posting, that theoretically speeds up the performance of your computer. The first & third commands take a snapshot of the performance of the computer before & after the update command is run. The `date` part embeds a timestamp into the name of the file, so you end up with files like "top_output_Tue Apr 10 10:05:52 EDT 2001". This way it's obvious when you ran the reports, how long the optimization step took, etc. If you want, you can put these three commands on the one line, separated by semi-colons, like this: top -w -l1 > "top_output_`date`.txt" ; sudo update_prebinding -root / ; top -w -l1 > "top_output_`date`.txt"
(If the display here goes across multiple lines, ignore that -- they really are one line.) The benefit of doing it in one line is that everything is automated, so you can walk away, make cofee, whatever, and when you come back your performance reports are ready & waiting for you. (Hey kids, welcome to the wonderfully useful world of Unix shell scripting... :). Once you have finished, you'll end up with something like the following, assuming that you ran the report from your home directory like I did: /Users/chris% ls total 64 drwxrwxrwx 2 chris staff 264 Mar 26 15:20 Desktop drwxr-xr-x 3 chris staff 264 Dec 4 11:59 Documentation drwxr-xr-x 18 chris staff 568 Apr 9 14:10 Documents drwxr-xr-x 17 chris staff 534 Apr 9 15:00 Library drwx------ 5 chris staff 126 Mar 26 16:02 MailAccounts drwx------ 7 chris staff 194 Mar 26 16:02 Mailboxes drwxrwxrwx 6 root wheel 264 Sep 13 2000 PS to PDF Filter.pkg drwxr-xr-x 4 chris staff 264 Oct 17 16:38 Public -rw------- 1 chris staff 5358 Apr 10 09:56 top_output_Tue Apr 10 09:56:06 EDT 2001.txt -rw------- 1 chris staff 4096 Apr 10 10:05 top_output_Tue Apr 10 10:05:52 EDT 2001.txt /Users/chris%
The bottom two files are the ones we're interested in. To see them, you can open them in the Finder like you may be used to, or you can simply display them from the command line, like this: more top_output*
You can type out the full filenames, but using the asterisk catches everything that begins with "top_output", which should just be the two files we're interested in. This will present you with a big table full of data. If you don't understand what you're seeing, try the man page for the top command: man top
I won't bother explaining those details, but that should get you started. I'd be interested in learning if this gets a clear picture of how peformance might change by applying the optimizer. If you have followed this so far, you could get more data by taking periodic snapshots of the top command before & after running the optimizer, and comparing the performance of big applications like IE across that time frame. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.50 seconds |
|