• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

will Seti@home take advantage of a smp setup?

T

theProfessorX

Junior Member
Just wondering if Seti has code that will take advantage of a dual processor setup. I purchased several components and am going to fit them all in my new antec case this weekend.
 
The SETI software (GUI or CLI) wasn't written to take advantage of SMP, but the CLI will run two instances just fine. The easiest way is to use SETIDriver along with the CLI version and set the number of "Instances" to 2. You can also select "Processor Affinity", but I'm not sure as it is necessary. I run SETI on a Tiger MP with Dual XP1800+'s using SETIDriver and it's run flawlessly for almost a year! 🙂

I think you can also manually run two instances of CLI, but I personally think SETIDriver is much easier.

You can find the CLI and SETIDriver information in the SETI link in my sig! 🙂

Welcome to the TeAm again...enjoy! 🙂

Also, if this isn't enough info, just ask...we'll all be glad to tell more! 😉
 
Thanks for the info. I spent some time today setting up the CLI Seti client on my spare machines using the faq. Boy, it is much faster than the GUI client. I am seeing around a 3 fold speed increase per workunit. 3 or 4 hours per WU instead of 12 to 14. Made a huge difference.

I will set it up using your recommendation on my new server when I get ye olde windowsXP installed and patched up asap. Spent some time this afternoon getting everything nice and tidy in my new case and getting my raid array set up.

Once again thanks!

Prof

 
I'm one of those "others" that runs two instances of the CLI. 😉

At the time that I tried SetiDriver, which was probably a couple versions ago, I had problems getting it running; the CLI on the other hand was very easy to setup. I made two directories, calling them SETI1 and SETI2, put a copy of the CLI in each, and then configured the parameter switches:

c:\seti1\seti1.exe -verbose -cpu 1

c:\seti2\seti2.exe -verbose -cpu 2

I find it helpful to use the SetiSpy in conjunction with the CLI too, but that's up to you. 🙂

 
Originally posted by: networkman
I'm one of those "others" that runs two instances of the CLI. 😉
Click to expand...
I am yet another of those "others". I'm currently running two instances on my dual XP1800+ rig.

 
I am also one of those others! You will find that seti on a dual is 5-10% slower per WU. However, you only have one MB, one PSU, one hard drive and etc. which more than offsets the slight increase in WU time.
 
I am also one of those others! You will find that seti on a dual is 5-10% slower per WU. However, you only have one MB, one PSU, one hard drive and etc. which more than offsets the slight increase in WU time.
 
I am also one of those others! You will find that seti on a dual is 5-10% slower per WU. However, you only have one MB, one PSU, one hard drive and etc. which more than offsets the slight increase in WU time.
 
I am also one of those others! You will find that seti on a dual is 5-10% slower per WU. However, you only have one MB, one PSU, one hard drive and etc. which more than offsets the slight increase in WU time.
 
I am also one of those others! You will find that seti on a dual is 5-10% slower per WU. However, you only have one MB, one PSU, one hard drive and etc. which more than offsets the slight increase in WU time.
 
I am also one of those others! You will find that seti on a dual is 5-10% slower per WU. However, you only have one MB, one PSU, one hard drive and etc. which more than offsets the slight increase in WU time.
 
I am also one of those others! You will find that seti on a dual is 5-10% slower per WU. However, you only have one MB, one PSU, one hard drive and etc. which more than offsets the slight increase in WU time.
 
I am also one of those others! You will find that seti on a dual is 5-10% slower per WU. However, you only have one MB, one PSU, one hard drive and etc. which more than offsets the slight increase in WU time.
 
I am also one of those others! You will find that seti on a dual is 5-10% slower per WU. However, you only have one MB, one PSU, one hard drive and etc. which more than offsets the slight increase in WU time.
 
^
|

what a nef 😉

I also am one of the "others", but use SetiLogger and SetiWatch to keep an eye on the home fleet 🙂

 
wow cakin, thst quite a multi post 🙂

I use setiDriver for dual proc systems. no problems yet.
 
Wow Cakin! :Q
Impressive. 😀 😛

<echo>
I am also one of those "others" who run SETI on my duallies (dual Xeon and dual XP). And yes, unless your CPU has a cache of 1MB or higher, you will see a bit of a hit against your WU times. But it's still nice to get a goodly number of WUs out of one box. 😀
</echo>
 
I also ran SETI on my dual Tualatin (1.26GHz) setup. Ran pretty good 4-5 hours per unit. But I am one of those who switched to RC5 for the remainder of the project. WHich by the way needs more support. We are slipping!! But I do on average about 1400 blocks per day for RC5.
 
See what a good duallie setup can do for you! When combined with DirecWay and Mozilla you can SuperNef with only one click of the mouse.

It has made it even more fun with Paypal!
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top