Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Community > Team MacNN > Seti Crunch Time

Seti Crunch Time
Thread Tools
Fresh-Faced Recruit
Join Date: Jul 2001
Location: Rochester, NY
Status: Offline
Reply With Quote
Dec 11, 2001, 06:50 PM
 
I realize that people have asked time for crunching a seti packet in other post but I thougt I would ask again.

I have a QS 800DP (with 1.25gb ram) and run SETI on it whenever its on, which is most fo the time. When I not at my machine and at night I close all the other apps except SETI. It still takes my machine almost 16 hours to crunch a SETI packet which seems slow to me. Ive checked and I have the latest gui and terminal versions of SETI. I usual run the gui minimized becuase it seem faster than that terminal app.

Anyone have any ideas as to why SETI is so slow?

Also I have kernel panic daily on my machine, it started after I ungraded to 10.1. I can not figure out what causes them and the only app thats always running is SETI. Anyone have simialr problems or should I contact Apple and see if its a hardware problem?

Thanks
Joe
     
Administrator
Join Date: May 2000
Location: California
Status: Offline
Reply With Quote
Dec 11, 2001, 07:45 PM
 
Try turning off the GUI client, and running two copies of the CLI version. In 6-7 hours on your QS, both should finish up a work unit each.

If they seem to be running slow, open a 3rd terminal window, and type "top" followed by Return. You will get a process listing, including the percentage of CPU each process is using. The two SETI processes should be about even at 40-48 percent each.

Kernel panics are usually caused by unsupported hardware issues (usb devices, sometimes), or hardware faults. If you really suspect a hardware fault, run your Hardware Test CD on your unit. To test for unsupported hardware, try pulling 3rd party PCI cards and peripherals. Run without them for a day or two, see if the panics go away. If they do, you will have to try a few 3rd party addons at a time, until you find the problem one(s).
     
Mac Elite
Join Date: Jul 2001
Status: Offline
Reply With Quote
Dec 12, 2001, 12:28 PM
 
Jesus. I get 16 hours with my 500 iMac. Your top of the line G4 should be severaal times faster than mine.
Actual conversation between UCLA and Stanford during a login on early Internet - U: I'm going to type an L! Did you get an L? S: I got one-one-four. L! U:Did you get the O? S: One-one-seven. U: <types G> S: The computer just crashed.
     
Professional Poster
Join Date: Sep 2000
Location: Carbondale, IL
Status: Offline
Reply With Quote
Dec 12, 2001, 02:28 PM
 
iBook 300mhz, 192MB, OS 9.1 20hours
AIM: bmichel5581
MacBook 2.2 GHz Intel Core 2 Duo
4GB RAM
160GB
     
   
Thread Tools
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Top
Privacy Policy
All times are GMT -5. The time now is 11:45 PM.
All contents of these forums © 1995-2011 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.7 © 2000-2011, Jelsoft Enterprises Ltd., Content Relevant URLs by vBSEO 3.3.2