Seti@Home optimized science apps and information
Optimized Seti@Home apps => Linux => Topic started by: Quasar8000 on 15 Mar 2009, 02:39:06 pm
-
Hey everyone, I've been using BOINC to crunch for SETI for quite a long time. I found this site a couple of days ago and absolutely loved the idea (I didn't love the credits and computation time I wasted though ;)) I currently have 3 PCs running BOINC. one has Windows 7 x64 which I'm assuming there's no optimized app for yet, and the other two have 32-bit Linux. I downloaded optimized apps for these two systems. One of the systems is working without problems (so far), but the other keeps giving me a computation error a couple of seconds after I start every SETI task. The PC has an Athlon 64 3000+ with SSE2 capabilities. I downloaded the latest 32-bit SSE2 apps (r112) and followed the instructions that were attached with the files. I'm only using BOINC so I guess I'm only crunching Astropulse WUs, and I tried 3 of them, all of which gave me the same error 6-7 seconds after starting the task. Any ideas on what could be causing this?
-
Can you give us a link to your systems?
-
This is the PC that's been giving me the computation errors:
http://setiathome.berkeley.edu/show_host_detail.php?hostid=4681290
And this is the one that's working OK:
http://setiathome.berkeley.edu/show_host_detail.php?hostid=4642793
-
What SSE level your CPU supports?
-
SSE2. I double checked it using "cat /proc/cpuinfo" and CPU-Z (I have Windows XP installed on the PC too but I don't usually use it).
Sorry I forgot to add that I'm using BOINC 6.4.5 in case it makes any difference.
-
SSE2. I double checked it using "cat /proc/cpuinfo" and CPU-Z (I have Windows XP installed on the PC too but I don't usually use it).
Sorry I forgot to add that I'm using BOINC 6.4.5 in case it makes any difference.
Are you sure that you've downloaded the proper package ?
Try this one --> http://calbe.dw70.de/astrop/V5/ap500_503_linux_x32_sse2.tar.bz2
-
Hey everyone, I've been using BOINC to crunch for SETI for quite a long time. I found this site a couple of days ago and absolutely loved the idea (I didn't love the credits and computation time I wasted though ;)) I currently have 3 PCs running BOINC. one has Windows 7 x64 which I'm assuming there's no optimized app for yet,
Actually you can use the optimized apps for Windows with no problem at all. You might be able to run one of Raistmer's packages on it, I will let someone else talk about that though.
For the Mac, I would suggest this package for a little pick me up (http://www.arkayn.us/seti/OSX_V8_AP5_CORE2DUO.zip).
-
SSE2. I double checked it using "cat /proc/cpuinfo" and CPU-Z (I have Windows XP installed on the PC too but I don't usually use it).
Sorry I forgot to add that I'm using BOINC 6.4.5 in case it makes any difference.
Are you sure that you've downloaded the proper package ?
Try this one --> http://calbe.dw70.de/astrop/V5/ap500_503_linux_x32_sse2.tar.bz2
That's strange, the package I downloaded (http://lunatics.kwsn.net/index.php?module=Downloads;sa=dlview;id=179) was the same version you gave me a link to, but I think their sizes are not the same. In any case, using the new package I'm now at 3 minutes in my task calculation with no errors ;D Thanx a lot for the help. I'll report back on how the tasks go.
Hey everyone, I've been using BOINC to crunch for SETI for quite a long time. I found this site a couple of days ago and absolutely loved the idea (I didn't love the credits and computation time I wasted though ;)) I currently have 3 PCs running BOINC. one has Windows 7 x64 which I'm assuming there's no optimized app for yet,
Actually you can use the optimized apps for Windows with no problem at all. You might be able to run one of Raistmer's packages on it, I will let someone else talk about that though.
For the Mac, I would suggest this package for a little pick me up (http://www.arkayn.us/seti/OSX_V8_AP5_CORE2DUO.zip).
I'd love to know if there's an optimized package that I can use for Astropulse on 64-bit Windows. I looked in the Downloads section but couldn't find anything. And I'll definitely use the package you recommended for the Mac. Thank you for the tips ;D
-
That's strange, the package I downloaded (http://lunatics.kwsn.net/index.php?module=Downloads;sa=dlview;id=179) was the same version you gave me a link to, but I think their sizes are not the same. In any case, using the new package I'm now at 3 minutes in my task calculation with no errors ;D Thanx a lot for the help. I'll report back on how the tasks go.
Since you're already past 3 min, it should work. ;)
-
I got two WUs and they're already finished!!! Each of them showed an expected CPU time of about 290 hours but one finished in a little over 3 minutes and the other in a little over 6 minutes. It seems both finished without errors but I wanted to check if this is normal. Here are the WUs:
http://setiathome.berkeley.edu/result.php?resultid=1185956268
http://setiathome.berkeley.edu/result.php?resultid=1186361087
-
The key is this line.
Found 30 single pulses and 30 repeating pulses, exiting.
As long as the wingmate finds the same thing, it should all be good.
-
I got two WUs and they're already finished!!! Each of them showed an expected CPU time of about 290 hours but one finished in a little over 3 minutes and the other in a little over 6 minutes.
I'm using the SSE3-App and need about 25-30 hours for one WU. I still wonder if the calculations are correct, as performance gain of the optimized app is about 4 times (roughly estimated), compared with the default app.
All your WUs seem to have the same result, there is definitely something wrong.
-
I'm using the SSE3-App and need about 25-30 hours for one WU. I still wonder if the calculations are correct, as performance gain of the optimized app is about 4 times (roughly estimated), compared with the default app.
That's why they are called "optimized" apps. That are waaayyy faster than stock apps. Don't worry, science done is the same.
All your WUs seem to have the same result, there is definitely something wrong.
Definitely there is something wrong with his computer.
@Quasar8000: Is your PC overclocked? RAM checked ok?
-
I have recently had a AP-WU marked as invalid (http://setiathome.berkeley.edu/workunit.php?wuid=417591258). I used the SSE2-app on my notebook (http://setiathome.berkeley.edu/show_host_detail.php?hostid=4851459). This WU took 46 hours to compute while a second WU (http://setiathome.berkeley.edu/workunit.php?wuid=417591604) is at 60:48:00 with 73.25% done =>83 hours total. A third WU running at the moment seems to be taking about 45 hours again. Will see what the results of these two are, but there might be a slight problem with the SSE2-AP.
I still have to do a memtest though, but the last time about two months ago everything was correct.
EDIT: The third WU (http://setiathome.berkeley.edu/workunit.php?wuid=417924453) finished after 16 hours with "30 single pulses and 30 repeating pulses". There is definitely something wrong.
-
That could be a random thing. Watch this machine for a few more WUs and report back.
Edit:
EDIT: The third WU (http://setiathome.berkeley.edu/workunit.php?wuid=417924453) finished after 16 hours with "30 single pulses and 30 repeating pulses". There is definitely something wrong.
No, right now, it doesn't mean anything. We have to wait for another wingman to return his result to see if your result is good or no. Nevertheless if you want to test the stability of your machine run prime95 ( http://www.mersenne.org/freesoft ) for at least 8h (some like to run at least 24h).
Edit2: T2300 should support sse3. You can gain a slight increase in computation speed switching from sse2 to sse3 app.
-
Had Memtest running last night (about 10 hours), no errors detected.
And http://setiathome.berkeley.edu/workunit.php?wuid=417591604 is finished, found 30 single pulses and is inconclusive.
Nevertheless if you want to test the stability of your machine run prime95 ( http://www.mersenne.org/freesoft ) for at least 8h (some like to run at least 24h).
Running right now.
T2300 should support sse3. You can gain a slight increase in computation speed switching from sse2 to sse3 app.
That's the information in Wikipedia and intels datasheet, but /proc/cpuinfo just tells me
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon bts pni monitor est tm2 xtpr pdcmI guess the "ss" should be sse3 or ssse3
-
That's the information in Wikipedia and intels datasheet, but /proc/cpuinfo just tells me
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon bts pni monitor est tm2 xtpr pdcmI guess the "ss" should be sse3 or ssse3
nx is sse3.
-
That's the information in Wikipedia and intels datasheet, but /proc/cpuinfo just tells me
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon bts pni monitor est tm2 xtpr pdcmI guess the "ss" should be sse3 or ssse3
nx is sse3.
I disagree. SSE3 was originally called Prescott New Instructions, and is shown as pni in that list (Windows Vista may also use the pni code). The nx code means an execution protection mechanism which allows marking memory regions for data only, not executable instructions. Early Prescott chips didn't have nx but obviously did have pni/SSE3, early AMD Athlon 64 chips had nx but not SSE3.
Joe
-
I disagree. SSE3 was originally called Prescott New Instructions, and is shown as pni in that list (Windows Vista may also use the pni code). The nx code means an execution protection mechanism which allows marking memory regions for data only, not executable instructions. Early Prescott chips didn't have nx but obviously did have pni/SSE3, early AMD Athlon 64 chips had nx but not SSE3.
Joe
I stand corrected. :)
-
mprime didn't find any problem in 20 hours, my system seems fine. What's left is a buggy app or there is a bug in the CPU that is triggered by an instruction which is used in the optimized AP but not in mprime.
-
Lysius, what tests did you run? small ffts, large ffts, blend?.
Let this machine do a few more WUs and we'll see how it goes. Also, as we've said earlier you can switch to a SSE3 app.
-
Lysius, what tests did you run? small ffts, large ffts, blend?.
Blend ran for 20 hours, large ffts runs for 10 hours now without an error. I think I will do small ffts next.
EDIT:
I'm running http://setiathome.berkeley.edu/workunit.php?wuid=417924453 now an my Desktop PC with the SSE2 and the SSE3 AP.
I guess pulse.out is what would be send to the server. I have attached these for both apps (after 40 minutes of running). The SSE3-app doesn't seem to have found anything by now, the SSE2-app found 30 pulses already (almost immediately after start).
EDIT2: I have downloaded the app from http://calbe.dw70.de/linux32.html in case that matters. The link at http://lunatics.kwsn.net/optimized-applications-release-news/optimized-astropulsev5-5-03-r112-for-linux-osx-transitional-package.msg15103.html;topicseen#msg15103 does not work.
[attachment deleted by admin]
-
I don't think we can compare the two results in the middle of computation. Wait for them to end and then we can compare the results.
Yes, the Linux 32 bit AstroPulse_v5 5.03_SSE2 + 5.00 (INTEL/AMD) (transitional package) link is broken.
-
...
EDIT:
I'm running http://setiathome.berkeley.edu/workunit.php?wuid=417924453 now an my Desktop PC with the SSE2 and the SSE3 AP.
I guess pulse.out is what would be send to the server. I have attached these for both apps (after 40 minutes of running). The SSE3-app doesn't seem to have found anything by now, the SSE2-app found 30 pulses already (almost immediately after start).
...
The 30 single pulses found by the SSE2 app are all at DM 911 and less. The app starts at DM 896 and goes to 15103, so if the SSE3 app hasn't found any and has run at least 1% of the work, it's clear the results won't match.
Lysius, would you upload that WU as an attachment here? Archive it with Zip, 7Zip, or RAR so it has an acceptable extension, not that it will compress much. I think the evidence indicates there's a flaw in the SSE2 app, having a WU which demonstrates the flaw would help.
Joe
-
The SSE3-App now has found something at DM 7023.
I have attached the WU.
[attachment deleted by admin]
-
Rerunning your wu, Lysius. Using AP SSE2 application from Crunch3r's page on my T7200, openSuSE 11.1, KDE4.2. If there is something wrong with this application this host should fail as well. It's now half an hour into that wu with ca. 20 hours to go.
-
The SSE3-App now has found something at DM 7023.
I have attached the WU.
Thanks, and I apologize for listing Windows archivers rather than gzip and bzip2 which would have made sense here.
Because the WU showed signals very early on the SSE2 build I changed the <dm_high> value to 1023 [1] and ran it with the Windows ap_5.03r112_SSE.exe app with my Pentium-M system. No reportable pulses were found, the best_pulses all had peak_power well below threshold.
[1] We use changes to <dm_low> (which needs to be a multiple of the <dm_chunk_large> value) and <dm_high> (which can be any value higher than <dm_low>) to make AP WUs for standalone testing which run fairly quickly. If the difference is less than the <dm_chunk_large> value the crunch time is 1/111 of a full run.
Joe
-
I'm also running this wu with sse2 and sse3 32bit apps from crunch3r's page. Sometime on Tuesday I should have the results.
I don't know if it is of importance or no but these 2 apps are different from the ones I, and probably also Urs, have tested during the testing phase where there was no problem found. On the other hand the 32bit sse and 64bit sse3 apps from crunch3r's page are the same with the ones we tested. I don't know what crunch3r changed.
-
Both are finished now. The SSE3-App actually took longer than the SSE2-App.
SSE3:
real 1475m25.372s
user 1363m40.233s
sys 86m3.655sSSE2:
real 1429m15.220s
user 1317m58.278s
sys 86m18.336s
[attachment deleted by admin]
-
They are different. Lysius can you also run the two clients attached below?. They are the ones we've tested before release.
[attachment deleted by admin]
-
Lysius can you also run the two clients attached below?. They are the ones we've tested before release.
Running for about 50minutes now, no pulse has been found so far. This SSE2-App seems better, but final results will take something like another 24 hours.
-
Ok. I'm still running the two apps I got yesterday from crunch3r's page. Next I'll run the two apps I attached above and my 64bit sse3 app. With this I've run more than a 100 WUs without a single problem, not even a third wingman-arbiter was needed in any of them AFAIK. This will be our reference.
-
I have used the 32-bit SSE3-App from crunch3r's Page (sha1sum: 2551c1a0553aa696327bd26d0bd4866446bb9018) on my Desktop PC (E6750) with about 15 WUs, 5 left for validation, the rest validated without a problem. So this app seems to be OK, too (at least much better than the SSE2).
-
I have recognized, that Indices.txt (that is generated while running AP; is there any information on what this file, fold.dat and wisdom.dat do?) is the same for both SSE3-apps and the "correct" SSE2-app, but differs for the broken SSE2-app. I have attached both versions.
[attachment deleted by admin]
-
Lysius, sunu, i can see the same. The linux 32bit SSE2 release version is definitly broken. My tests are still running, but this far into the wu it is obvious. After i saw sunu's post about the last prerelease version earlier today, i looked that one up and started parallel another test. After some more hours the intermediate pulse.out files are too different to compare to each other.
Results should be ready by tomorrow.
-
Urs, it's not only broken, it's more than that. :D
It gives results that they are not only wrong but inconsistent. My results are weakly similar or different compared to Lysius's.
My sse3 (from crunch3r's page) results are strongly similar to Lysius's results.
Now I've started the two apps I've posted above (fortunately I keep everything from my tests) and then the 64bit sse3 app. We've tested these apps, but no harm doing them again. By tomorrow evening I think we'll finish.
Lysius I don't know what the other files do exactly, maybe Joe Segur will enlighten us. Nevertheless pulse.out is the one returned to berkeley with the results so it is the file that matters.
-
fold.dat is part of checkpoint set, wisdom.dat is FFTW library wisdom file (FFTW try to keep best FFT algorithm between its runs), indices.txt - some info file about what areas were blanked in particular task.
Result file is pulse.out indeed.
-
Thanks raistmer.
-
I have pulled my SSE2 package until you get to the root cause of the problem.
-
Arkayn it's possible that your SSE2 package has already a good AP client. What is the date of the AP client in your package? Can you attach it here?
-
My testruns with the different SSE2 AstroPulse applications (prerelease and release) just finished. The results are different.
add: Send Crunch3r a pm about the testresults.
[attachment deleted by admin]
-
The release apps are much faster than the prerelease (both SSE2 and SSE3). Both prerelease apps are at 1550m CPU-Time now, which is more than the release-apps took and they still did not find the pulses at <dm>-14010</dm> yet.
Because the results of the SSE2-app are quite random, I would guess at least some memory initialization has been "optimized" away.
-
I guess I'm a bit late to the party here, but it's only recently that I noticed that a Linux machine of mine was _very_ quickly processing away the astropulse units it got (the machine is mostly unattended, so I didn't notice this immediately).
All of them finished within about 15 seconds max. The log from one of these:
<core_client_version>6.4.5</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
AstroPulse v. 5.03
Linux 32 bit
FFTW USE_CONVERSION_OPT USE_SSE2->SSE3_EMU
SIGILL: illegal instruction
Stack trace (7 frames):
[0x80797d4]
[0xb7f62400]
[0x8059020]
[0x8049e14]
[0x8048d58]
[0x8217824]
[0x8048131]
Exiting...
</stderr_txt>
]]>
(Link: http://setiathome.berkeley.edu/result.php?resultid=1192493744)
I'm quite (but not 100%) sure I installed the SSE2 apps. I have now installed the SSE apps, but have to wait until an ap unit is going to be crunched, to see if this fixed it...
Regards, Patrick.
-
[size=0]I guess I'm a bit late to the party here, but it's only recently that I noticed that a Linux machine of mine was _very_ quickly processing away the astropulse units it got (the machine is mostly unattended, so I didn't notice this immediately).
All of them finished within about 15 seconds max. The log from one of these:
<core_client_version>6.4.5</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
AstroPulse v. 5.03
Linux 32 bit
FFTW USE_CONVERSION_OPT USE_SSE2->SSE3_EMU
SIGILL: illegal instruction
Stack trace (7 frames):
[0x80797d4]
[0xb7f62400]
[0x8059020]
[0x8049e14]
[0x8048d58]
[0x8217824]
[0x8048131]
Exiting...
</stderr_txt>
]]>
(Link: http://setiathome.berkeley.edu/result.php?resultid=1192493744)
I'm quite (but not 100%) sure I installed the SSE2 apps. I have now installed the SSE apps, but have to wait until an ap unit is going to be crunched, to see if this fixed it...
Regards, Patrick.[/size]
Patrick, thanks for reporting your problem. I colorized the part in the quoted output of your post that identifies the AstroPulse SSE2 application version in question. This is the bad one definitely. To use the SSE version until this problem gets resolved is recommended.
-
[size=0]I guess I'm a bit late to the party here, but it's only recently that I noticed that a Linux machine of mine was _very_ quickly processing away the astropulse units it got (the machine is mostly unattended, so I didn't notice this immediately).
All of them finished within about 15 seconds max. The log from one of these:
<core_client_version>6.4.5</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
AstroPulse v. 5.03
Linux 32 bit
FFTW USE_CONVERSION_OPT USE_SSE2->SSE3_EMU
SIGILL: illegal instruction
Stack trace (7 frames):
[0x80797d4]
[0xb7f62400]
[0x8059020]
[0x8049e14]
[0x8048d58]
[0x8217824]
[0x8048131]
Exiting...
</stderr_txt>
]]>
(Link: http://setiathome.berkeley.edu/result.php?resultid=1192493744)
I'm quite (but not 100%) sure I installed the SSE2 apps. I have now installed the SSE apps, but have to wait until an ap unit is going to be crunched, to see if this fixed it...
Regards, Patrick.[/size]
Patrick, thanks for reporting your problem. I colorized the part in the quoted output of your post that identifies the AstroPulse SSE2 application version in question. This is the bad one definitely. To use the SSE version until this problem gets resolved is recommended.
Speedimic (http://setiathome.berkeley.edu/forum_thread.php?id=52524&nowrap=true#876353) and Officedude (http://setiathome.berkeley.edu/forum_thread.php?id=52577&nowrap=true#876231) both had this error about 15 days ago on hosts 4462906 (http://setiathome.berkeley.edu/show_host_detail.php?hostid=4462906) and 3370265 (http://setiathome.berkeley.edu/show_host_detail.php?hostid=3370265), Speedimic tried to redownload the same SSE2 app,
but the link was Broken by then, suspect that might have been from Lunatics, Both have swapped to the SSE app.
Claggy
-
Done. Results of the prerelease apps are exactly identical. The results are very similar to the ones of the released SSE3-app (peak power differs slightly, and one of the time_series differs in one digit). I have attached all results (including those from the released apps) and a diff between the nearly identical results.
My result is identical to Urs' for the prerelease.
All "good" apps have the same indices.txt that is produced right at the beginning of the calculation and it differs significantly from the broken app. Although it is of no use after the calculation, it might be the cause of the miscalculation (or the difference has the same origin), so i would start there when searching for the bug.
EDIT: For the comparison of the performance
prerelease SSE2:
real 1847m42.197s
user 1703m37.728s
sys 93m4.481sprerelease SSE3:
real 1777m46.620s
user 1631m52.455s
sys 93m21.558srelease SSE2:
real 1429m15.220s
user 1317m58.278s
sys 86m18.336srelease SSE3:
real 1475m25.372s
user 1363m40.233s
sys 86m3.655s
[attachment deleted by admin]
-
I got all the results from Lysius, Urs and mine and compared each other and I agree with what you've all said above. So to recap:
SSE2 app from Crunch3r's page is not good.
SSE3 app from Crunch3r's page and pre-release apps I've posted above are good.
So for the time being, till Crunc3r makes a new one, everyone who wants a SSE2 app you can use the one attached.
-
Checking results :
at first the ones that are supposed to be ok :
.../ap_5.03/linux/ap_5.03_sse2_lx32_r03/compare> ls
pulse_503pr_sse2.out pulse.out_pre pulse.out_rel_SSE3 pulse.out_SSE3 rescmpAP2
.../ap_5.03/linux/ap_5.03_sse2_lx32_r03/compare> ./rescmpAP2 pulse_503pr_sse2.out pulse.out_pre
\: <ap_signal>14,<pulses>4,<best_pulses>10
: <ap_signal>14,<pulses>4,<best_pulses>10
All Signals: Checked 14, 14 , Strongly Similar
Pulses: Checked 4, 4 , Strongly Similar
Best Pulses: Checked 10, 10 , Strongly Similar
.../ap_5.03/linux/ap_5.03_sse2_lx32_r03/compare> ./rescmpAP2 pulse_503pr_sse2.out pulse.out_rel_SSE3
\: <ap_signal>14,<pulses>4,<best_pulses>10
: <ap_signal>14,<pulses>4,<best_pulses>10
All Signals: Checked 14, 14 , Strongly Similar
Pulses: Checked 4, 4 , Strongly Similar
Best Pulses: Checked 10, 10 , Strongly Similar
.../ap_5.03/linux/ap_5.03_sse2_lx32_r03/compare> ./rescmpAP2 pulse_503pr_sse2.out pulse.out_SSE3
\: <ap_signal>14,<pulses>4,<best_pulses>10
: <ap_signal>14,<pulses>4,<best_pulses>10
All Signals: Checked 14, 14 , Strongly Similar
Pulses: Checked 4, 4 , Strongly Similar
Best Pulses: Checked 10, 10 , Strongly SimilarThey 'are strongly similar.
Now against the ones from that bad release version :.../ap_5.03/linux/ap_5.03_sse2_lx32_r03/compare> ls
pulse_503pr_sse2.out pulse_503rel_sse2.out pulse.out_pre pulse.out_rel_SSE2 pulse.out_rel_SSE3 pulse.out_SSE2 pulse.out_SSE3 rescmpAP2
.../ap_5.03/linux/ap_5.03_sse2_lx32_r03/compare> ./rescmpAP2 pulse_503pr_sse2.out pulse_503rel_sse2.out
\: <ap_signal>14,<pulses>4,<best_pulses>10
: <ap_signal>40,<pulses>30,<best_pulses>10
All Signals: Weakly similar or Different.
Pulses: Weakly similar or Different.
Best Pulses: Weakly similar or Different.
.../ap_5.03/linux/ap_5.03_sse2_lx32_r03/compare> ./rescmpAP2 pulse_503pr_sse2.out pulse.out_rel_SSE2
\: <ap_signal>14,<pulses>4,<best_pulses>10
: <ap_signal>40,<pulses>30,<best_pulses>10
All Signals: Weakly similar or Different.
Pulses: Weakly similar or Different.
Best Pulses: Weakly similar or Different.
.../ap_5.03/linux/ap_5.03_sse2_lx32_r03/compare> ./rescmpAP2 pulse_503pr_sse2.out pulse.out_SSE2
\: <ap_signal>14,<pulses>4,<best_pulses>10
: <ap_signal>40,<pulses>30,<best_pulses>10
All Signals: Weakly similar or Different.
Pulses: Weakly similar or Different.
Best Pulses: Weakly similar or Different.They are obviously (no. of signals) different.
-
So for the time being, till Crunc3r makes a new one, everyone who wants a SSE2 app you can use the one attached.
I think I will do some performance comparison tomorrow and run the SSE-version. Might be that the SSE-version of the released app is faster than the SSE2-version of the prerelease. Can you also attach the SSE-version of the prerelease?
-
The sse app in crunch3r's page is the same we had for testing, it didn't change. And it is slower than the sse2 app.
-
I got all the results from Lysius, Urs and mine and compared each other and I agree with what you've all said above. So to recap:
SSE2 app from Crunch3r's page is not good.
SSE3 app from Crunch3r's page and pre-release apps I've posted above are good.
So for the time being, till Crunc3r makes a new one, everyone who wants a SSE2 app you can use the one attached.
Okidoki, I installed the app you attached. However, until my BOINC install begins with ap units (none in sight yet), I cannot comment if it works. I do hope I'm not going to mess up more stuff for my wingmen...
Regards, Patrick.
-
Arkayn it's possible that your SSE2 package has already a good AP client. What is the date of the AP client in your package? Can you attach it here?
This is the version that is in the SSE2 combined package. I downloaded it from this site when it was made available.
[attachment deleted by admin]
-
Patrick it's good, there is no concern.
Arkayn this client is different from both the bad one and the pre-release one. I've started testing it. Tomorrow I'll have the results.
-
I wonder if it is the SSE version then.
We really need to rename the files so we can tell what they are without having to run them or look at the code.
-
I wonder if it is the SSE version then.
We really need to rename the files so we can tell what they are without having to run them or look at the code.
In original sources USE_SSE* in stderr defines what SSE level should be used on targed hosts. So you can rename apps based on this value
-
Arkayn your client is sse2 all right. In a few hours it should finish.
-
I started with the OS X versions and renamed them with the revision number so anybody can tell what version they have.
After this is cleaned up, I hope to get the Linux apps renamed as well.
-
Arkayn your client is good. It's also faster than the pre-release app I've posted above.
Anyone who wants an SSE2 app is advised to get arkayn's file from post #51 above.
-
Arkayn your client is good. It's also faster than the pre-release app I've posted above.
Anyone who wants an SSE2 app is advised to get arkayn's file from post #51 above.
So that means I should forget about the app you attached? Perhaps you can also edit that post of yours to 'lessen' the confusion?
Regards, Patrick.
-
I forgot, done!
-
I forgot, done!
Well, the machine in question just dumped the two ap units it had queued up, errorlog from one:
<core_client_version>6.4.5</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
AstroPulse v. 5.03
Linux 32 bit
FFTW USE_CONVERSION_OPT USE_SSE2->SSE3_EMU
SIGILL: illegal instruction
Stack trace (7 frames):
[0x80797d4]
[0xb7f6f400]
[0x8059020]
[0x8049e14]
[0x8048d58]
[0x8217824]
[0x8048131]
Exiting...
</stderr_txt>
]]>
What went wrong here? I installed the latest ones advised here...
Regards, Patrick.
-
PatrickV2,
this looks like an error i had in an earlier test phase, its because of a bug (typo). Better don't use this version.
-
PatrickV2,
this looks like an error i had in an earlier test phase, its because of a bug (typo). Better don't use this version.
I installed the attached one, which people upthread claimed were 100% OK. I just re-enabled work to this host, got an ap unit, which bombed after 6 secs. Task:
http://setiathome.berkeley.edu/result.php?resultid=1201141711
So, which version of the apps should I install/use?
Regards, Patrick.
-
Speedimic tried that app again, after i had PM'd him saying that there was an SSE2 app that worked,
But he's got the same errors as before,
<stderr_txt>
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
AstroPulse v. 5.03
Linux 32 bit
FFTW USE_CONVERSION_OPT USE_SSE2->SSE3_EMU
SIGILL: illegal instruction
Stack trace (7 frames):
[0x80797d4]
[0xb7f53420]
[0x8059020]
[0x8049e14]
[0x8048d58]
[0x8217824]
[0x8048131]
Exiting...
</stderr_txt>
Host 4462906 (http://setiathome.berkeley.edu/show_host_detail.php?hostid=4462906) AMD Athlon(tm) 64 Processor 3200+ [Family 15 Model 31 Stepping 0]
Claggy
-
Currently i rerun some tests on this problem and try to find a working SSE2 version.
-
Urs, have you had any problems with arkayn's app? Here (http://lunatics.kwsn.net/4-linux/linux-ap-optimisation.msg15362.html#msg15362) is Crunch3r's response from something else, but maybe applies here also. These two hosts have only errored out workunits within a few seconds and nothing else. I can't be so lucky to not have anything.
-
Urs, have you had any problems with arkayn's app? The app you attached is two days older than the pre-release app I've already posted and tested good.
-
Yes, arkayn's version fails on native SSE2 only hardware (like a Pentium M for example) reproducable immediately after the wisdom.dat file is created.
A package with a working optimized SSE2 version is attached.
[attachment deleted by admin]
-
Yes, arkayn's version fails on native SSE2 only hardware (like a Pentium M for example) reproducable immediately after the wisdom.dat file is created.
A package with a working optimized SSE2 version is attached.
I installed this one, re-enabled work-fetch, but promptly got 65 Seti MB WUs with not an ap unit in sight. :(
I'll report back when/if the machine processes an ap unit...
Regards, Patrick.