|Sep 27, 2002, 09:03 PM||#1|
SETI@home benchmark results on Dual 1.25GHz G4
I've been doing benchmark tests on my new Dual 1.25GHz Power Mac G4.
Here are my SETI@home results.
The notation xx:yy:zz means xx hours, yy minutes, zz seconds. I averaged times from multiple work units to get more accurate results. One work unit took an hour less than all the others (sometimes SETI determines that a work unit is useless and aborts its computations early), so I omitted that run from the results.
1. The minimum "Average CPU time per work unit" was achieved running the CLI (command line interface) version of SETI, with the energy saver features turned off and no other processes running.
CPU time: 5:40:48 (baseline)
Elapsed time: 5:40:50 (baseline)
CPU utilization: 100% (baseline, meaning one processor fully occupied)
Explanation: This is the fastest that this Mac can run. Nothing but Mac OS X 10.2, the Terminal application, and SETI were running. Only one CPU was used. Mac OS overhead is extremely minimal (a few seconds in over 5 hours).
2. CLI version, energy saver on:
CPU time: 5:48:09 (2.2% over baseline)
Elapsed time: 5:49:30 (2.5% over baseline)
CPU utilization: 98%
Explanation: A little more Mac OS overhead, but essentially the same.
3. Screensaver (graphical) version, energy saver on, graphics display timeout after 30 minutes:
CPU time: 5:52:11 (3.3% over baseline)
Elapsed time: not measured
CPU utilization: 97%
Explanation: This is a typical way you might use SETI@home. The graphical display (for 30 minutes) adds a little overhead, but not much, since one CPU can handle the graphics while the other is still number crunching the work unit.
4. CLI version, energy saver off, with 2 copies of SETI@home running at once:
CPU time: 11:47:57 total
5:53:59 per unit (3.9% over baseline)
Elapsed time: 5:56:55 total (4.7% over 1 unit baseline, but for 2 units!)
2:58:28 per unit
CPU utilization: 191%
Explanation: I got twice the amount of number crunching done (2 units completed) in only a few minutes more elapsed time than when I did 1 unit. The second CPU is in almost constant use. Good for you, Dual Mac!
5. CLI version, energy saver off, with 3 copies of SETI@home running at once:
CPU time: 17:45:20 total
5:55:07 per unit (4.2% over baseline)
Elapsed time: 8:56:37 total (57% over 1 unit baseline, but for 3 units)
2:58:52 per unit
CPU utilization: 191%
Explanation: You can run 3 (or more) units at essentially the same rate as 2 units, i.e., nnn units will take nnn/2 as much elapsed time as 2 units. Both CPUs will be almost fully occupied. Process switching adds neglible overhead.
* To benefit from dual CPUs, run 2 or more SETI@home processes at the same time in CLI mode.
* Energy saver settings have minimal effect.
* With one SETI@home processing running, it is OK to leave the graphics display on. But you might as well set it to time out if you won't be watching it.
* Having dual processors lets you complete units at twice the elapsed time rate of a single processor of the same speed by running two or more SETI processes at once. In this case, set the screen to go dark (no graphics) if you use the screensaver version, since both CPUs will already be occupied.
* The measure of "Average CPU time per work unit" (as shown on the SETI summary pages) will be slightly less when running multiple processes at once. The results when you run dual processes on dual processors will appear the same as if you run two separate single-processor computers that have the same CPU speed.
And that's enough benchmarking for one week!
|Oct 18, 2002, 05:00 PM||#3|
how do you run 2 seti's???
just got a new dual 1 gig -my times while doing lots of other stuff (final cut, photoshop, web and so on) is around 8 or 9 hours. but 2 at once when i go home sounds very cool.
|Oct 18, 2002, 05:13 PM||#4|
You need to be running OSX. Once in OSX, all you need to do is install SETI twice (into sepearate directories). You have to use the CLI version (not the screensaver version). Below is the link to the CLI version.
Eg. SETI1 + SETI2. Then fire up the clients manually or use a program such as SETICNTL to manage the clients (no need to mess around with the command line). You can get SETICNTL from :
Just do a search and you will find it.
|Oct 18, 2002, 05:23 PM||#5|
ummm - sep direct???
how do i install on a sep directory?
i use a mac to do print graphics for a living (and video editing on the side) - they pay peopel to fix it when there is a prob. -
i got the 2nd version of seti, but dont know where to install it. is a directory another disc? lol probably wrong.
|Oct 18, 2002, 05:33 PM||#6|
When you install the Command Line Interface (CLI) version, you pick a folder (directory) to install it in, e.g., /Applications/seti1.
In a Terminal window, you can then make a second copy of the application using the commands to copy a directory:
cp -r seti1 seti2
To start one running in a Terminal window, you can type
To start a second copy running at the same time, open a new (i.e., second) window in the Terminal application and in it type
You can stop either one at any time by pressing Control-C while that Terminal window is the active window.
The very first time you run setiathome, it interviews you about your user name and any team you want to join. I recommend the MacRumors team!
|Oct 18, 2002, 05:38 PM||#7|
Re: SETI@home benchmark results on Dual 1.25GHz G4
|Oct 18, 2002, 10:57 PM||#8|
I tried nice 20 but I can't really tell the difference, so I run them at the default of nice 0, even when I'm working on other things.
I have a theory that the graphical version runs as quickly as the CLI version because the video card (a third processor in your dual processor machine!) is handling the graphics.
How to get stats
In a Terminal window (other than the one running setiathome, you can check the progress in the current work unit as follows:
cd /Applications/seti1 (or wherever)
grep prog state.sah
The output will be something like this:
which means it is 14.159265% of the way done with that work unit.
You can check the number of cpu seconds used so far on the current work unit with
grep cpu state.sah
You can check the total cpu seconds used for all previous work units submitted to Berkeley with
grep cpu user_info.sah
I wrote myself a shell script to do these commands, so I can find out where I stand anytime I have a sudden need to know.
Finally, you can check when a command (setiathome in this case) started (to compute elapsed time) with the ps -u command.
|Oct 19, 2002, 12:11 AM||#9|
After running the CLI version for a while, I tried SETI Menu. While it took a little tweaking, I like it. It takes almost no cycles and it gives me current statistics. Not a huge advantage over opening a terminal window, but a small one, nonethless (IMHO).
I'm interested if others have tried it.
"If you would be a real seeker after truth, it is necessary that at least once in your life you doubt, as far as possible, all things."
|Thread Tools||Search this Thread|
|thread||Thread Starter||Forum||Replies||Last Post|
|FS: Loaded Powermac Dual 1.25Ghz G4 with Cinema Display||Wano||Marketplace Archive 2||9||May 13, 2006 12:19 PM|
|FS: DUAL 1.25Ghz G4. LOADED!||Wano||Marketplace Archive 1 (Posts count)||0||Jan 18, 2005 03:25 PM|
|WTB: Dual 1.25Ghz G4||Wano||Marketplace Archive 1 (Posts count)||2||Feb 22, 2003 01:51 AM|
|How long until the Dual 1.25GHz G4 is obsolete?||Doctor Q||Hardware Rumors||41||Sep 22, 2002 02:49 AM|
All times are GMT -5. The time now is 12:43 AM.