I don't totally get rid of the downgrade problems.
I upgraded the hardware of one host which was crunching with app. 4.31. Now that box is SSE capable and uses 4.27. To keep on working with the WUs branded for 4.31 I added a block to the app_info.xml that is directing the 4.31 work to 4.27.
Same thing on my other host which tried the 64Bit 4.28 app. Here the block is redirecting 4.28 work to 4.27.
Bad thing about this is, that all downloaded new work is branded to be crunched with the highest app version, 4.31 and 4.28.
That's probably no real problem since the hosts keeps on working, but all finished work gets the wrong stamp.
I guess, I have to manualy edit the client_state.xml files to solve these problems?
Ok, I finished 2 WUs which took more than 41 ks instead of <25 ks. :(
At least it's really positive that there finally is a start in the 64Bit era. :)
Reading the AMD specs about 64Bit coding and optimizing for speed gives the impression to me, that it might be a lot of work until this app is performing well.
Imho it would be a good idea to give the source to some volunteer developers, because work done for 64Bit apps will probable be of little benefit for 32Bit apps. On the other side I don't think it will take too long until the 32Bit era is over.
cu,
Michael
Agree Here,
using Ubuntu Gutsy 64 Bit,
Lots of software run well with the Box.Yet, most I.E. Java/Flash/P2P, run as a 32
packages.Am not able to see any noticeable speed difference with the O.C.
Will be quite happy when a reply comes in my email ,from this thread, saying the O.C. works on 64bitPC,s Well W2g Einstein.And the engineers that compile it.Good Luck all.
"Happy Crunching"
@ Bernd
I assume you use a server side script to check the results of all these beta and power apps? So we don't have to flag results like this one to you ;-)
Both results crunched with 4.28 have the validate status "Checked, but no consensus yet". :(
So I think, when the third results come in, the results done with the 4.28 app will be invalid.
My results were valid, it's just that they took as long as the stock 32 bit app to process, so I went back to the 32 bit 4.27 app, which has since been replaced by the 32 bit 4.35 app.
I don't totally get rid of
)
I don't totally get rid of the downgrade problems.
I upgraded the hardware of one host which was crunching with app. 4.31. Now that box is SSE capable and uses 4.27. To keep on working with the WUs branded for 4.31 I added a block to the app_info.xml that is directing the 4.31 work to 4.27.
Same thing on my other host which tried the 64Bit 4.28 app. Here the block is redirecting 4.28 work to 4.27.
Bad thing about this is, that all downloaded new work is branded to be crunched with the highest app version, 4.31 and 4.28.
That's probably no real problem since the hosts keeps on working, but all finished work gets the wrong stamp.
I guess, I have to manualy edit the client_state.xml files to solve these problems?
cu,
Michael
RE: Ok, I finished 2 WUs
)
Agree Here,
using Ubuntu Gutsy 64 Bit,
Lots of software run well with the Box.Yet, most I.E. Java/Flash/P2P, run as a 32
packages.Am not able to see any noticeable speed difference with the O.C.
Will be quite happy when a reply comes in my email ,from this thread, saying the O.C. works on 64bitPC,s Well W2g Einstein.And the engineers that compile it.Good Luck all.
"Happy Crunching"
@ Bernd I assume you use a
)
@ Bernd
I assume you use a server side script to check the results of all these beta and power apps? So we don't have to flag results like this one to you ;-)
http://einsteinathome.org/workunit/37007110
Win 4.26 didn't validate against Linux 4.28
Both results crunched with
)
Both results crunched with 4.28 have the validate status "Checked, but no consensus yet". :(
So I think, when the third results come in, the results done with the 4.28 app will be invalid.
http://einsteinathome.org/workunit/36832261
http://einsteinathome.org/workunit/36831701
Did anybody get valid results?
cu,
Michael
My results were valid, it's
)
My results were valid, it's just that they took as long as the stock 32 bit app to process, so I went back to the 32 bit 4.27 app, which has since been replaced by the 32 bit 4.35 app.
I can confirm that this App
)
I can confirm that this App version is not only slow, but also gives invalid results in some cases.
Thank you for testing this App. Please don't use it anymore and switch to a recent 32Bit version (e.g. 4.38).
BM
BM