Just finished the first WU with the Linux 4.35 app, considerably slower than 4.21.
Computers results
The one reported on "23 Aug 2007 5:16:07 UTC" is the first 4.35 result, looks like the ones in progress will be very close to that CPU time.
This seems to depend on the CPU type, I've seen other CPUs where 4.35 runs faster than 4.21. This might be caused by a single instruction, FLDCW , which is used in floating point to integer conversion. It can take anything from 4 to > 100 CPU cycles depending of what CPU you are using. Both Intel and AMD have filed fancy patents on how to best implement this tricky instruction so that it runs faster. I guess Akos could expand on this better than me.
Ok, hope theres a new app version in progress then, if this affects all Core2 CPUs then theres a lot of wasted CPU seconds coming up.
I had the stupid idea that i would switch back to 4.21. It worked fine and expected time to completion was going down to the old 4.21 level, but when i tried to get more work it didnt go so well, all WUs i had crashed and so did the ones Boinc tried to download. I guess i shouldnt try that again, or is there any way to make it work?
Ok, hope theres a new app version in progress then, if this affects all Core2 CPUs then theres a lot of wasted CPU seconds coming up.
I had the stupid idea that i would switch back to 4.21. It worked fine and expected time to completion was going down to the old 4.21 level, but when i tried to get more work it didnt go so well, all WUs i had crashed and so did the ones Boinc tried to download. I guess i shouldnt try that again, or is there any way to make it work?
You can have either the most recent "official" version installed (that will download automatically eventually after you delete the app_info.xml file from teh einstein projects directory (but it might crash existing results). Or you can install a beta version. Technically this can be any beta version, even if it's not the most recent.
However, speed is not everything, and each new release also fixes some bugs so you really should only have either the most recent official or beta version (the newest Linux beta version probably has the same performance than the current official one).
However, speed is not everything, and each new release also fixes some bugs so you really should only have either the most recent official or beta version (the newest Linux beta version probably has the same performance than the current official one).
Speed is not everything, he says. Now that 4.37 is the official Linux app, I got a new WU with it... 151.5 hours estimated from the beginning. Let's see what the end time will be. :-)
However, speed is not everything, and each new release also fixes some bugs so you really should only have either the most recent official or beta version (the newest Linux beta version probably has the same performance than the current official one).
Speed is not everything, he says. Now that 4.37 is the official Linux app, I got a new WU with it... 151.5 hours estimated from the beginning. Let's see what the end time will be. :-)
Is the RDCF reset to 1.0 with each new app version, maybe? One of my machines has a RDCFs as low as 0.37, most are around 0.5.
New app, good. Cant wait to try 4.37, unfortunately i managed to get too big work cache and my last experiment in changing app manually didnt end very good. Maybe that app_info.xml file is worth a try, should i just delete it and then Boinc will download 4.37 next time a WU is reported?
Good news is that its so F'in cold outside (4c last night) that main rig is left crunching around the clock now, and even then the room temp stays on the low side. This is the season for high vcore and serious overclocking, the longest season of the year =D
New app, good. Cant wait to try 4.37, unfortunately i managed to get too big work cache and my last experiment in changing app manually didnt end very good. Maybe that app_info.xml file is worth a try, should i just delete it and then Boinc will download 4.37 next time a WU is reported?
Better to set the project to No New Tasks first, run down your cache if there's any left, report everything. Exit BOINC, delete app_info.xml (and if you want the einstein 4.37 app), restart BOINC and reset the project, then Allow New Tasks.
RE: Just finished the first
)
This seems to depend on the CPU type, I've seen other CPUs where 4.35 runs faster than 4.21. This might be caused by a single instruction, FLDCW , which is used in floating point to integer conversion. It can take anything from 4 to > 100 CPU cycles depending of what CPU you are using. Both Intel and AMD have filed fancy patents on how to best implement this tricky instruction so that it runs faster. I guess Akos could expand on this better than me.
CU
BRM
Ok, hope theres a new app
)
Ok, hope theres a new app version in progress then, if this affects all Core2 CPUs then theres a lot of wasted CPU seconds coming up.
I had the stupid idea that i would switch back to 4.21. It worked fine and expected time to completion was going down to the old 4.21 level, but when i tried to get more work it didnt go so well, all WUs i had crashed and so did the ones Boinc tried to download. I guess i shouldnt try that again, or is there any way to make it work?
Team Philippines
RE: Ok, hope theres a new
)
You can have either the most recent "official" version installed (that will download automatically eventually after you delete the app_info.xml file from teh einstein projects directory (but it might crash existing results). Or you can install a beta version. Technically this can be any beta version, even if it's not the most recent.
However, speed is not everything, and each new release also fixes some bugs so you really should only have either the most recent official or beta version (the newest Linux beta version probably has the same performance than the current official one).
CU
BRM
RE: However, speed is not
)
Speed is not everything, he says. Now that 4.37 is the official Linux app, I got a new WU with it... 151.5 hours estimated from the beginning. Let's see what the end time will be. :-)
RE: RE: However, speed is
)
Is the RDCF reset to 1.0 with each new app version, maybe? One of my machines has a RDCFs as low as 0.37, most are around 0.5.
CU
H-BE
Oops, edit. Mine's 1 exactly,
)
Oops, edit. Mine's 1 exactly, yes. Hmm...
New app, good. Cant wait to
)
New app, good. Cant wait to try 4.37, unfortunately i managed to get too big work cache and my last experiment in changing app manually didnt end very good. Maybe that app_info.xml file is worth a try, should i just delete it and then Boinc will download 4.37 next time a WU is reported?
Good news is that its so F'in cold outside (4c last night) that main rig is left crunching around the clock now, and even then the room temp stays on the low side. This is the season for high vcore and serious overclocking, the longest season of the year =D
Team Philippines
RE: New app, good. Cant
)
Better to set the project to No New Tasks first, run down your cache if there's any left, report everything. Exit BOINC, delete app_info.xml (and if you want the einstein 4.37 app), restart BOINC and reset the project, then Allow New Tasks.
Can't go wrong that way.
RE: [snip] I will run out
)
I've had errors with XP, but never any with Linux (ubuntu)