A new Linux App is available from our Beta Test page.
This is a "switching" App as you already know from the 4.38 App.
If something goes wrong with the automatic switching (i.e. you get "signal 4" "illegal instruction" errors), placing a file named "CPU_TYPE_0" in the BOINC directory should run the generic (non-SSE) App even if the wrapper would detect SSE.
The SSE App was built with compiler settings that should use the SSE unit for most arithmetics (-mfpmath=sse). There might be a difference in speed overall in one or the other direction, but mainly it should serve two purposes: first we try to avoid the FPU exceptions by avoid using the FPU, and second it should improve the prefetching of the Hough code (actually enable parts of it). This means that the App should run faster and further reduce the variance in run-times between workunits compared to previous versions.
In addition the App was built with BOINC API as of May 7, which means that it should work properly with latest development clients.
The app_info.xml has entries for
420
421
424
427
431
435
438
449
If your current App version is not listed here, you'll have to add it manually.
BM
BM

GNU/Linux S5R3 App 4.49 available for Beta test
)
Too bad. Are there SSE2 instructions in the executable?
Does the CPU_TYPE_0 work for the moment?
BM
BM
It indeed did contain SSE2
)
It indeed did contain SSE2 instructions. I built a new SSE App and updated the archive (and the md5sum on the page).
Thanks for the report.
BM
BM
RE: 1. Is it possible, that
)
Yes, it is possible, but I simply don't know.
That reminds me that I wanted to post some "reference workunit" for direct speed comparison. Will pick this up soon.
Not in speed. I still want to test the new BOINC API version, though, that's in both Apps, in particular with the latest Core Clients.
BM
BM
RE: RE: Switched from
)
Yep. Switching App versions in the middle of a Task is not supported in BOINC. In case of the "separate graphics" Apps this means that the "graphics_app" link in the slot directory is not updated and points to a file that doesn't exist anymore after installing a new App version. It is only set up new when a new Task is started.
BM
BM
RE: RE: RE: 1. Is it
)
For now I put a copy of the SSE2 App executable in http://einstein.phys.uwm.edu/power_apps/einstein_S5R3_4.49_1_i686-pc-linux-gnu.gz. This isn't a full-featured App package, you'll have to replace the file "einstein_S5R3_4.49_i686-pc-linux-gnu_1" in the 4.49 Beta Test App package with that (expanded) file.
BM
BM
RE: RE: Hi all! I would
)
The overall speedup in the App compared to 4.38 mainly comes from prefetch compiler intrinsics placed in the Hough code that require these switches. Another bit of speedup arises from changes in the Assembler-coded "Kernel loop" (the "interleaving" of SSE and FPU commands we have in the 4.42 MacOS Intel App), but I think that this effect will be larger on modern Intel CPUs (Core2) than on AMDs.
My guess is that the SSE2 App will be slightly faster if you would measure it against the SSE one, but you'll only notice the difference if you'd run the same workunit side by side e.g. on a dual core machine. It shouldn't be worth another case distinction in a "switching App".
BM
BM
RE: RE: For now I put a
)
Nope. I fixed the archive.
BM
BM
RE: For now I put a copy of
)
Yes, depending on the unpacking procedure this usually requires renaming the file.
BM
BM
RE: Great stuff,
)
Thanks, but most kudos should go to Bikeman and Akos for their great work!
BM
BM
RE: I just installed the
)
Switching Apps in the middle of a task usually confuses the run-time estimation, but I don't precisely know why.
BM
BM