plz explain why My X2 @ 2450 outscoring my 165 @ 2.9

[[cTx]Philosophy]

x2 has 8k some 165 has 6k some 165 was installed first and its getting ownd by the X2?

X2 3800 @ 2450 2X512 ch-5 underclocked because one of the dimms is blown @ below 180for 2-2-2
there clocked at like 166 some i think

165 @ 2.9 2X 1024 be-6 2.5-3-2-5 243 mhz getting ownd by underclocked X2 on a shidy os install thats 3 yrs old almost?

Wierd I tell ya

[[XC] Adywebb]

Have you checked to see how many results each has waiting to be validated?

You may find that the 165 has many more waiting than the X2 3800 and when they come through the scores will look different.

You can check by signing in at WCG and going to My Grid>Device Manager>Results Status and using the various filters.

[Hymay]

Yeah, it seems its going to take more than a couple days for the credits and validation averages to start kicking in. Kinda sucks when you knock a wu out in 3-4 hrs and it takes someone else 24+ hrs of runtime to validate it =)

[[cTx]Philosophy]

As of 12:35 today
I dont see how it shows the X2 as of having a full day more run time than the opty, theres just no way thats possible...

[carl.h]

Looks like you got loads of WU`s pending validation.

I believe something is wrong atm, I have 22 WU`s pending.

[Hymay]

As of 12:35 today
I dont see how it shows the X2 as of having a full day more run time than the opty, theres just no way thats possible...

Yeah, that screenie only shows the amt of wu's that have been validated. On the right, under Device manager, click on Results Statistics.. then count up the number of them pending. I had over 40 pending still. It'll also tell you if they were valid results, perhaps there is an unknown problem and one machine is not returning valid results? No clue how wcg handles computational errors.

Otherwise, if all is well, it'll just take a few days for the number of validations to catch up to the avg number you complete a day. you will always have a "cache" of pending tho, but eventually it should even out. somewhat.

[[XC] Adywebb]

As of 12:35 today
I dont see how it shows the X2 as of having a full day more run time than the opty, theres just no way thats possible...

Looks to me like you are crunching Aids stuff - is that right?

I would say that the opty is awaiting a load of WU's to be validated, if you go by the runtime the opty has done 14 results in 2 days (7 per day) so in 3 days you would expect it to have completed 21 - 4 more than the X2.

Aids WU's take alot longer than Cancer (and vary in length) - however if we look at an average runtime of around 4 hours, then the opty will have completed over 16 hours more work over 3 days than the X2 - so I think things look a bit brighter for you on Opty v X2 front

I hope my explaination makes some sense - I apologise if it doesn't.

[Hymay]

Looks like you got loads of WU`s pending validation.

I believe something is wrong atm, I have 22 WU`s pending.

I have over 40.. but I crank em out 2 every 3.5-4 hrs on the conroe, and about 2 every 5 hrs on the X2. Most "normal" people in wcg are running AXP's or so, and it takes em a "wee tad" longer to compute your same wu to validate it. Then it takes 6 hrs to update, etc, etc, Or mebbe you got unlucky and stuck with my buddy's "box" 266, I think it takes 48+ hrs to crunch a single result.

[meshmesh]

I have over 40.. but I crank em out 2 every 3.5-4 hrs on the conroe, and about 2 every 5 hrs on the X2. Most "normal" people in wcg are running AXP's or so, and it takes em a "wee tad" longer to compute your same wu to validate it. Then it takes 6 hrs to update, etc, etc, Or mebbe you got unlucky and stuck with my buddy's "box" 266, I think it takes 48+ hrs to crunch a single result.

It may be even worse than 48+. If one of the WUs have been downloaded by a nutter who likes to fill his work cache on his computer (has his "connect to server every" = 7 days, for example), then your result, and the second user's result as well, will not be validated until either that nutter gets around to crunching the third WU or even worse it just sits in his queue until it expires. At that time the server gives up on him and issues you guys the credit.

So forget about finding out so soon. Suggest you wait till october first, then evaluate your daily output through the whole month of September. That will give you an accurate figure.

I crunched malaricontrol a few times, and would be surprised at first when I get some unexpected credit from malaricontrol while doing 24/7 on Roseeta!

Look at it this way, you crunched the work, the check is coming in the mail.

[carl.h]

@ Hymay

Nahhhh, I think the validator is duff, loads of us Teddies with unvalidated WU`s atm.

Not that far behind you with my D930 @ 3.4 and the 3800+ X2 @ 4100

I don`t run 24/7 (long story), that`s what drags me back, 16/7 tops !

Meshmesh, I got one still waiting from the 22nd, go round and tell the nutter to connect will ya please !!!

[[XC] Adywebb]

Meshmesh, I got one still waiting from the 22nd, go round and tell the nutter to connect will ya please !!!

Sorry Carl didn't realise it was you - I will run off and connect now


@ meshmesh - very good advice :thumbsup:

[Hymay]

@ Hymay

Nahhhh, I think the validator is duff, loads of us Teddies with unvalidated WU`s atm.

Not that far behind you with my D930 @ 3.4 and the 3800+ X2 @ 4100

I don`t run 24/7 (long story), that`s what drags me back, 16/7 tops !

Meshmesh, I got one still waiting from the 22nd, go round and tell the nutter to connect will ya please !!!

Aye we agree there, meant in that post that I have over 40 unvalidated wu's when I counted last... loads n loads..

[[cTx]Philosophy]

whats it mean when it sais error, I have like 4 of em error
My cpus are stable, is this a messup?
or maybe arestart in middle, I heard they dont resume like rosey did..

Is this true

Also just changed all them over to cancer, forgot to do that last time..
My dad has had every type of cancer known to man almost and hes still kicking 78 and still smokes 3 packs a dam day, stubborn old man and isnt gonna go until hes ready..

Cancer research FTW!!!

[[XC] hipno650]

thats why validating takes so long i get it now. i started yesterday and have 4wu's waiting to be validated. and three valid.

[itznfb]

i have 90 WU's pending. i have a couple invalid, and a couple inconclusive. the invalid and inconclusive are on my opty that is highly OCed and possibly not 100% stable

[[XC] 4X4N]

I just checked and have 36 wu's pending. This is with only 3 machines. A couple are from 8/23. This quorom system takes forever.

[[XC] Adywebb]

This is because some 'WU hogs' cache more than a couple of days worth and then take ages to crunch 'em, or they run out of time and WCG has to send out another one after a week to complete the quorum

[[XC] serlv]

I just checked and have 36 wu's pending. This is with only 3 machines. A couple are from 8/23. This quorom system takes forever.

I have a boatload pending, like money in the bank!

[Martijn]

I have a boatload pending, like money in the bank!

That is a lot!!

[[XC] hipno650]

I have a boatload pending, like money in the bank!

HOLY

[meshmesh]

i have 90 WU's pending. i have a couple invalid, and a couple inconclusive. the invalid and inconclusive are on my opty that is highly OCed and possibly not 100% stable

Ok. If you think about it, these two (couple) of WUs have wasted 4 hrs. If this happens once every 48 hours, you loose 8% of your credit!

So how about dropping the clock 5% and end up better?

Oh oh, why do I feel I just committed a major sin?

[meshmesh]

I just checked and have 36 wu's pending. This is with only 3 machines. A couple are from 8/23. This quorom system takes forever.

Up to seven days on rare occasions (check the expiry date).
But usually 75% would validate within 72 hours so far.

[itznfb]

dropping the clock

wtf does that mean?

[meshmesh]

wtf does that mean?

Sorry not very familiar with forum abbreviations.

dropping the clock

I was suggesting that maybe a reducion in the clock spead in the BIOS, say from 250MHZ to 240MHz for example would be beneficial. May help better stability and thus avoid WU errors and wasted CPU cycles.

[Martijn]

Sorry not very familiar with forum abbreviations.

It means 'what the ' (fill that in for yourself )

I was suggesting that maybe a reducion in the clock spead in the BIOS, say from 250MHZ to 240MHz for example would be beneficial. May help better stability and thus avoid WU errors and wasted CPU cycles.

This is XS, no downclocking here, I think it is getting time you should understand that