Bugger, just lost a whole lot of work units after updating to 4.49 SSE2.
After downloading 4.49 then downloading the SSE2 file and replacing the original 4.49 executable file, I changed it's name and restarted Boinc.
Can you see what is wrong, yes that's right, I forgot to set the executable attribute and lost all the work.
Have now set that attribute and awaiting Boinc to download new work, this may take awhile as Boinc Manager has decided that Einstein has to wait and downloaded a heap of Rosetta WU's instead, probably due to the number of Einstein failures.
I will wait to see if it all works before trying again on the other computers.
Well I am impressed with the 4.49 SSE2 application. I have now returned 3 work units and all have been done in under 5 hours, which I had not done before.
Previous best for a trough result was 18,900 seconds, my best now is 16,788 seconds and I have not reached the trough yet, only halfway there. This is about 11% improvement on 4.35, with more to come.
Have an AMD Opteron 285 @2.6GHz, Linux Fedora Core 3.
The SSE2 application has improved my times down to 15,761 seconds for the trough of 1103.00 Hz on my AMD 285, about 16% improvement on my previous lowest time with 4.35.
My AMD 275 has dropped times to 18,483 seconds with a similar amount of improvement from around 21,800 seconds.
Runs error free and validating fine, so thumbs up for the SSE2 application version.
Just completed the first workunit processed entirely with the SSE2 app. It has already validated successfully as well. I also plugged in 8 previous workunits (all 4.49 SSE) into the Ready Reckoner v3, and came up with an estimated run time of the workunit of 30227s. This finished in 29607s, for about a 2.1% gain on a TL-56 Turion X2. So, not as large a gain as seen on other architectures, but forward progress nonetheless. Will keep a close eye on the next several workunits to see if the gain is consistent.
DL'd the files, renamed the one to have the _1 at the end.
Copy and Paste and overwrite.
Restart Boinc.
It is still using 4.38
I believe my failure lies within the "executable attribute" that Conan and Tevault have posted aboot.
I have right clicked the files and they are set to read and write as well as the box 'allow file to execute as program'..... but I do not see an 'advanced' tab.
A little more clarity and information on the procedure or how to set this, please.
DL'd the files, renamed the one to have the _1 at the end.
Copy and Paste and overwrite.
Restart Boinc.
It is still using 4.38
Please check your file name carefully.
You should have a file of 4.6 MB
../BOINC/projects/einstein.phys.uwm.edu/einstein_S5R3_4.49_i686-pc-linux-gnu_1
which is set executable and with exactly that name.
If the name of your file is different, rename it. There should not be 4.49_1 in
the middle of the name!
The files 4.38 should be deleted.
1. set at no new work
2. copied files and overwrite'd app_info file
3. deleted 4.38 files
4. restarted system
5. boinc re-downloaded the 4.38 and resumed work at 4.38
1. set at no new work
2. copied files and overwrite'd app_info file
3. deleted 4.38 files
4. restarted system
5. boinc re-downloaded the 4.38 and resumed work at 4.38
what have I missed ?
Did you stop BOINC before you copied the files?
You don't have to restart the system! ;-)
If you already have some WUs at your system, BOINC will show that they are crunched by 3.38 even if it uses 4.49. This will change with the first new WU you download.
If you already have some WUs at your system, BOINC will show that they are crunched by 3.38 even if it uses 4.49.
The 'built at' information (generated by the E@H applications) is more reliable for identification than the version info supplied by BOINC.
$ strings einstein_S5R3_4.49_i686-pc-linux-gnu_1.SSE2 | grep -i 'built *at:'
This Einstein@home App was built at: May 14 2008 11:45:00
$ strings einstein_S5R3_4.49_i686-pc-linux-gnu_1.SSE | grep -i 'built *at:'
This Einstein@home App was built at: May 14 2008 17:58:40
$ strings einstein_S5R3_4.49_i686-pc-linux-gnu_0 | grep -i 'built *at:'
This Einstein@home App was built at: May 14 2008 12:41:04
5. boinc re-downloaded the 4.38 and resumed work at 4.38
I know you did, but you might want to check that the app_info.xml file rely got overridden.
Looks like it didn't.
Open it and verify it contains the lines for 4.49.
My 2 cents...
Alex.
God created a few good looking guys.. and for the rest he put hairs on top..
RE: RE: Bugger, just lost
)
The SSE2 application has improved my times down to 15,761 seconds for the trough of 1103.00 Hz on my AMD 285, about 16% improvement on my previous lowest time with 4.35.
My AMD 275 has dropped times to 18,483 seconds with a similar amount of improvement from around 21,800 seconds.
Runs error free and validating fine, so thumbs up for the SSE2 application version.
Just completed the first
)
Just completed the first workunit processed entirely with the SSE2 app. It has already validated successfully as well. I also plugged in 8 previous workunits (all 4.49 SSE) into the Ready Reckoner v3, and came up with an estimated run time of the workunit of 30227s. This finished in 29607s, for about a 2.1% gain on a TL-56 Turion X2. So, not as large a gain as seen on other architectures, but forward progress nonetheless. Will keep a close eye on the next several workunits to see if the gain is consistent.
Master....I have
)
Master....I have failed.
DL'd the files, renamed the one to have the _1 at the end.
Copy and Paste and overwrite.
Restart Boinc.
It is still using 4.38
I believe my failure lies within the "executable attribute" that Conan and Tevault have posted aboot.
I have right clicked the files and they are set to read and write as well as the box 'allow file to execute as program'..... but I do not see an 'advanced' tab.
A little more clarity and information on the procedure or how to set this, please.
running Ubuntu Hardy Heron
thanks for any help, insults or margarita's.
RE: DL'd the files,
)
Please check your file name carefully.
You should have a file of 4.6 MB
../BOINC/projects/einstein.phys.uwm.edu/einstein_S5R3_4.49_i686-pc-linux-gnu_1
which is set executable and with exactly that name.
If the name of your file is different, rename it. There should not be 4.49_1 in
the middle of the name!
The files 4.38 should be deleted.
I am running 4.49 on Debian without problems!
File name is correct. 1.
)
File name is correct.
1. set at no new work
2. copied files and overwrite'd app_info file
3. deleted 4.38 files
4. restarted system
5. boinc re-downloaded the 4.38 and resumed work at 4.38
what have I missed ?
RE: File name is
)
Did you stop BOINC before you copied the files?
You don't have to restart the system! ;-)
If you already have some WUs at your system, BOINC will show that they are crunched by 3.38 even if it uses 4.49. This will change with the first new WU you download.
cu,
Michael
RE: If you already have
)
The 'built at' information (generated by the E@H applications) is more reliable for identification than the version info supplied by BOINC.
$ strings einstein_S5R3_4.49_i686-pc-linux-gnu_1.SSE2 | grep -i 'built *at:'
This Einstein@home App was built at: May 14 2008 11:45:00
$ strings einstein_S5R3_4.49_i686-pc-linux-gnu_1.SSE | grep -i 'built *at:'
This Einstein@home App was built at: May 14 2008 17:58:40
$ strings einstein_S5R3_4.49_i686-pc-linux-gnu_0 | grep -i 'built *at:'
This Einstein@home App was built at: May 14 2008 12:41:04
The 3.38 applications were built in Feb, IIRC.
Regards,
Waldi
Hi ! RE: 2. copied
)
Hi !
I know you did, but you might want to check that the app_info.xml file rely got overridden.
Looks like it didn't.
Open it and verify it contains the lines for 4.49.
My 2 cents...
Alex.
God created a few good looking guys.. and for the rest he put hairs on top..
I opened the app_info file on
)
I opened the app_info file on all the afflicted machines.
The 4.49 is the only app that is listed.
hrmpf !
RE: I opened the app_info
)
Is your boinc-user allowed to execute the 4.49 app?