I understand the problem. But what's with the existing wu cache?
If we use your app_info with 4.02 (original client) and 4.10 (opt. client), then my cache (4.02 WU) didn't use the opt. client and we must flush it before can use the opt. right ?
After that the Einstein Server is sending 4.10er WUs ?
Great speed increase, just waiting for my WU cash to run dry so I can switch to the app patched with S5T0712 and renamed too 4.10. Just waiting too see how a correct app_info looks so many suggestions hear.
I understand the problem. But what's with the existing wu cache?
If we use your app_info with 4.02 (original client) and 4.10 (opt. client), then my cache (4.02 WU) didn't use the opt. client and we must flush it before can use the opt.
After that the Einstein Server is sending 4.10er WUs ?
You're actually free to run whatever app you want for the WUs designated for 4.02. I just immagine that Bernd would want to have 4.02 results crunched using official app, that's all.
You can have both parts of the app_info.xml identical except for the version number (402 and 410 that is).
[edit]
The only time a WU gets fixed to a certain application version is right after it's received by BOINC client. This ensures that WU will get crunched with the application which was available at the time it was given out. This can mean a lot of time with really long crunching times (as seen at CPDN). The magic about versions in the app_info.xml is needed because the versioning is in the client_state.xml. You could also edit that file ... it's just too risky to mess it somehow.
[/edit]
What you're concerned is probably the versioning. There's a simple rule: there aren't WUs version 4.02 and WUs version 4.10 ... there are only WUs that requre application einstein_S5R1 ... if you don't use app_info.xml, then new application may get downloaded with new WUs. Not so if using app_info.xml. Presence of app_info.xml just tells project scheduller that the only application there is is the one stated in the file.
The main intention of app_info.xml is where there's no official application for a given HW/SW platform but user could build one by themself (as it is possible at S@H). In that case project scheduller should just send work available for given application. Well, I guess project could 'outlaw' a particular application version if they wanted. I don't forsee that.
Hier schwirren mittlerweile soviele xml, zip und was weiß ich noch alles für Dateien umher das ich mal eine klare Aussage von dem Projektverantwortlichen hören will.
Schließlich wollen die ja auch das wir die WUs als 4.10 zurückschicken.
Ein einheitlicher Standard tut Not!
Here meanwhile as many xml, zip and other files still circulate I wish to hear a clear statement of the project responsible person. Finally those also who wants us to send back the WUs as 4,10.
A uniform standard does emergency!
Athlon
PS: in meiner Muttersprache schreib ich immer noch am besten. In Englisch hatte ich ne 4
Gary, how does your app_info
)
Gary, how does your app_info file looks?
@Metod, S56RKO I
)
@Metod, S56RKO
I understand the problem. But what's with the existing wu cache?
If we use your app_info with 4.02 (original client) and 4.10 (opt. client), then my cache (4.02 WU) didn't use the opt. client and we must flush it before can use the opt. right ?
After that the Einstein Server is sending 4.10er WUs ?
Great speed increase, just
)
Great speed increase, just waiting for my WU cash to run dry so I can switch to the app patched with S5T0712 and renamed too 4.10. Just waiting too see how a correct app_info looks so many suggestions hear.
Sorry it's 2.30am here in Oz
)
Sorry it's 2.30am here in Oz and I'm at a meeting at 7.30am so I'll give more info later.
Cheers,
Gary.
RE: @Metod, S56RKO I
)
You're actually free to run whatever app you want for the WUs designated for 4.02. I just immagine that Bernd would want to have 4.02 results crunched using official app, that's all.
You can have both parts of the app_info.xml identical except for the version number (402 and 410 that is).
[edit]
The only time a WU gets fixed to a certain application version is right after it's received by BOINC client. This ensures that WU will get crunched with the application which was available at the time it was given out. This can mean a lot of time with really long crunching times (as seen at CPDN). The magic about versions in the app_info.xml is needed because the versioning is in the client_state.xml. You could also edit that file ... it's just too risky to mess it somehow.
[/edit]
What you're concerned is probably the versioning. There's a simple rule: there aren't WUs version 4.02 and WUs version 4.10 ... there are only WUs that requre application einstein_S5R1 ... if you don't use app_info.xml, then new application may get downloaded with new WUs. Not so if using app_info.xml. Presence of app_info.xml just tells project scheduller that the only application there is is the one stated in the file.
The main intention of app_info.xml is where there's no official application for a given HW/SW platform but user could build one by themself (as it is possible at S@H). In that case project scheduller should just send work available for given application. Well, I guess project could 'outlaw' a particular application version if they wanted. I don't forsee that.
Metod ...
I'm confused ;) What's the
)
I'm confused ;)
What's the app_info.xml with 402 and 410 tells the project scheduler exactly ?
S5T0713.dat - eliminated
)
S5T0713.dat
- eliminated double jumps
- reduced amount of FPU macro ops
- removed double loads on general purpose registers
- better SSE register usage
- reduced memory and integer register usage
- optimized branch structure
- faster FPU comparisons
- SSE3 truncation
- some reordered instructions
- automatic SSE/SSE3 usage
- less FPU-memory-FPU operation
- shorter patch file :-)
CPU: ALL
app: einstein_S5R1_4.10_windows_intelx86.exe
RE: Okay, I´ve taken the
)
Seems to work correctly without droping WU´s.
Stay tuned and keep crunching
RE: S5T0713.dat -
)
And now a new ZIP file containing S5T0713...
more info some posts below...
Udo
Hier schwirren mittlerweile
)
Hier schwirren mittlerweile soviele xml, zip und was weiß ich noch alles für Dateien umher das ich mal eine klare Aussage von dem Projektverantwortlichen hören will.
Schließlich wollen die ja auch das wir die WUs als 4.10 zurückschicken.
Ein einheitlicher Standard tut Not!
Here meanwhile as many xml, zip and other files still circulate I wish to hear a clear statement of the project responsible person. Finally those also who wants us to send back the WUs as 4,10.
A uniform standard does emergency!
Athlon
PS: in meiner Muttersprache schreib ich immer noch am besten. In Englisch hatte ich ne 4
Stay tuned and keep crunching