Question on processing speed

[BlackMountainCow]

Hi!

Is it only for me or does your processing speed also drop when the WU contains high triples? Usually I process around 21 - 24% an hour, but when I have triples like 10 or higher my rate drops to 15 - 11 % an hour. Gaussians somehow don't seem to affect my processing rate.

Also it is 100% of the time, that my WU processing rate drops to 15 % or so when i reach about the middle of the WU, it stays low for 5 % of the WU, then it goes up again no the usual rate. And at the end (last 5 %) of a WU the rate increases to like 40%.

Is 21- 24 % a good rate for an AMD Athlon XP 1600+ , 512 DDR 266 RAM, WIN98 and SETI Hide with client 3.08 anyway?

I also noticed that setting the priority to high does not affect my processing speed at all though it makes my system very unstable.


Greetz


Christian

 

[Spacehead]

I've never noticed a relationship between triplets & processing speed. It could be that VLAR's contain more tripltes than "normal" WU's. VLAR's take longer to process.

Yes, processing slows down in the middle of the WU, with the 1st & last few % going quite fast.

My XP1800 averages about 29% per hour, so i'd say 21-24% is good.

About the client priority, i leave mine at low as like you said, raising it doesn't really help that much & slows down my computer.

 

[BlackMountainCow]

VLARs = very low angle recordings?

if so, when does a "very" low one start i. e. at which angle is the transition between a low and a very low one?

if not, what is a VLAR ?



thx


Christian

 

[Confused]

VLAR - Very Low Angle Range

An "average" AR is 0.417, and a LAR/VLAR is normally anything below about 0.1-0.2, depending on which way you're facing, the orientation of Mars, Jupiter and Alpha Centuri, the colour of the milk and the pitch of the dog barking next door, and who you're asking.







On Windows systems, these lower AR work units tend to take longer, with more of a performance hit when running a Win9x system as opposed to a NT based system. Linux seems to not make any difference to the time! Windows boxes also tend to do the higher angle ranges quicker also.

I have found that the "%/hr", or Estimated Time (if using SetiDriver) doesn't tend to level off until you get about 30-40% of the way into the Work Unit, and will report higher/quicker before it levels off. I don't know why...but that's what i've seen from all the systems and WUs i've crunched

Hope some of this information helps

Confused

 

[BlackMountainCow]

Thx for that info!

Now I'm realy "confused"

 

[Assimilator1]

lol Garry

BlackMountainCow
1 thing ,v3.03 is about 15% faster at average AR WUs.
Dunno about %/hr but my rig does average AR WUs in just under 2.5hrs ,thats an XP1700 @2.04GHz with dual DDR RAM.

Wanta link for v3.03 CLi?

 

[BlackMountainCow]

R u sure 3.03 is that much faster ?! Hell yeah, gimme that link!!

Btw, what about this ominous security hole? Is it that bad, like I have to take care of it in a different way then?

THX


Christian

 

[Confused]

The security thing is about getting the client to talk to a "fake server" as such. There is an easy way to implement that, and I know for sure that myself and Smokeball have done it on our SetiQueues, so if you use one of those queues, then you will be fine

Oh yeah, Seti@home 3.03 CLI link (hosted on my own server )

Confused

 

[Assimilator1]

BMC
Yep it is that much faster
Check out this thread for more info about v3.03 security fix

 

[BlackMountainCow]

Many THX for the help guys! I really appreciate that!

Greetz


Christian

 

[Assimilator1]

No probs