• 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.

Welcome to Team AnandTech SETI - hamburglar and Peter Valverius

Smoke

Smoke

Distributed Computing Elite Member
Welcome to Team AnandTech SETI! 😀

We are now 2,169 members strong. 🙂

I would like to introduce our newest members:

hamburglar ---- Rank 2169 New ---- 0 Wus 🙂 ---- Mentor: IJump
Here is your personal Stats Machine

Peter Valverius ---- Rank 935 New ---- 244 Wus 🙂 ---- Mentor: CADKindaGUY
Here is your personal Stats Machine

Your personal mentor will be contacting you shortly. He may not be able to contact you if you don?t have PMs enabled (Allow Private Messages) ? you can do that in your profile. 🙂

We hope you drop by often and say hello. 🙂

We like to recommend that all of our new members go to the following link and use the Preferred Method 2 Installation: SETI Help and Installation

To see a summary of new members for this month, check out: New Members ? September
 
Thanks for the warm welcomes. I have a question though. How do people get so many work units per day (100+) It took me 9+ hours to get first work unit. I have a p4 1.3 GHz. What does the speed depend on?
 
Originally posted by: hamburglar
Thanks for the warm welcomes. I have a question though. How do people get so many work units per day (100+) It took me 9+ hours to get first work unit. I have a p4 1.3 GHz. What does the speed depend on?
Click to expand...

Welcome to the Team 🙂

I am guessing you are using the GUI (screensaver) version. If you are, that is probably why your work unit was so long. The CLI is much faster than the GUI (up to 50% in some cases).

These people who have 100+ per day administrate big networks at work, and therefore are able to install it on lots of computers there. Some others who have around 30+ per day also have all of their own machines in their own house! networkman is one of these people 🙂

The speed of the work unit can depend on many things. The most important is the speed of your processor, cache size on the processor and also the speed of your RAM. Seti loves big caches (1mb is preferable, because the client is about 700k and therefore it can all fit into 1mb of cache without having to go to your RAM), fast FSB and RAM speed if you have less than 1mb cache and also CPU speed will come into effect if the others are constant.

Also something that affects the speed of a Work Unit is the Angle Range. The average angle range of a WU is 0.417. The higher the AR, the quicker the WU will tend to be, and the lower the AR the slower it will tend to be on a Windows machine. The HAR and LAR should both be a bit quicker, because there is less data to analyse, but for some reason the LAR (sometimes called VLAR, very low angle range) takes longer on a Windows machine. The hit on a Linux based machine is less.

I hope this has helped explain things a bit, and i hope to see you posting more soon 🙂

Confused
 
Originally posted by: Confused
Originally posted by: hamburglar Thanks for the warm welcomes. I have a question though. How do people get so many work units per day (100+) It took me 9+ hours to get first work unit. I have a p4 1.3 GHz. What does the speed depend on?
Click to expand...
Welcome to the Team 🙂 I am guessing you are using the GUI (screensaver) version. If you are, that is probably why your work unit was so long. The CLI is much faster than the GUI (up to 50% in some cases). These people who have 100+ per day administrate big networks at work, and therefore are able to install it on lots of computers there. Some others who have around 30+ per day also have all of their own machines in their own house! networkman is one of these people 🙂 The speed of the work unit can depend on many things. The most important is the speed of your processor, cache size on the processor and also the speed of your RAM. Seti loves big caches (1mb is preferable, because the client is about 700k and therefore it can all fit into 1mb of cache without having to go to your RAM), fast FSB and RAM speed if you have less than 1mb cache and also CPU speed will come into effect if the others are constant. Also something that affects the speed of a Work Unit is the Angle Range. The average angle range of a WU is 0.417. The higher the AR, the quicker the WU will tend to be, and the lower the AR the slower it will tend to be on a Windows machine. The HAR and LAR should both be a bit quicker, because there is less data to analyse, but for some reason the LAR (sometimes called VLAR, very low angle range) takes longer on a Windows machine. The hit on a Linux based machine is less. I hope this has helped explain things a bit, and i hope to see you posting more soon 🙂 Confused
Click to expand...

You mean the Command line client server is faster right? does it work for winxp?
My comp specs are:
1.3 GHz
512 Cache
384 RDRAM 800.

I was wondering if i can install this on my hosted web site as well. I can get into command prompt in my webserver so I was wondering if that would be enough to get SETI working on that comp as well. Will it hog up too much of the server's resources?

Thanks for your help
 
You mean the Command line client server is faster right? does it work for winxp?
My comp specs are:
1.3 GHz
512 Cache
384 RDRAM 800.

I was wondering if i can install this on my hosted web site as well. I can get into command prompt in my webserver so I was wondering if that would be enough to get SETI working on that comp as well. Will it hog up too much of the server's resources?

Thanks for your help
Click to expand...

Yeah it's much faster because the CPU doesn't have to process the graphics, which you look at 1% of the time it's running and think about how pretty it is, and then go away 😀

Check this site out TeAm Anandtech SETI Install Guide on how to install it etc..

And welcome to the greatest team on the planet!!
 
You *may* be able to get it running on the webserver, but i wouldn't hold too much hope.

As for it using resources, if anything else (like the web hosting 😉) needs the CPU then it will allow the other app to use the CPU 🙂


And yeah, the CLI can be much faster 🙂 Just follow the link and instructions that DJSnairdA gave you 🙂

And don't have to use Orangekid's proxy (like it suggests there), you could use any one listed in this thread. Feel free to use mine if you wish, there aren't many users (just a couple of people from the miniteam British Bulldog Racers) 🙂


Confused
 
Nicely explained Confused🙂(copied for future use😉) ,1 thing I will add though is that the hit to VLAR WU times to WinXP & Win2k is far less than Win95,98 & ME.
eg on Win98se with Ath XP I used to get about 3hrs30mins for an av AR WU, & upto about 5hrs with a VLAR WU!:disgust: ,with Win2k I got about 3hrs 25mins for an av AR WU & a max of 3hrs 50mins with a VLAR WU🙂
 
Thanks for the welcomes again. And yes, the console proggy is must faster. Instead of taking 9.5 hours, it only takes me about 6 hours. Thanks!
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top