Message boards :
Number crunching :
Lunatics Windows Installer v0.41 Release Notes
Message board moderation
Previous · 1 . . . 4 · 5 · 6 · 7 · 8 · 9 · 10 . . . 17 · Next
Author | Message |
---|---|
[B^S] madmac Send message Joined: 9 Feb 04 Posts: 1175 Credit: 4,754,897 RAC: 0 |
|
Grant (SSSF) Send message Joined: 19 Aug 99 Posts: 13746 Credit: 208,696,464 RAC: 304 |
BOINC probably thinks you have enough work for the time being. You should see it asking for more as time passes (and before your cache is completely dry), but everything is going to be a little bit out of line for a day or two until it settles down. And then some. I did the update this morning before going to work. Almost 12 hours later & the Result Duration Correction Factor is down to 0.3 & 0.2, CPU run times are pretty close, but the GPU ones are still way over the top (3hrs for WUs that are taking around 15min). Grant Darwin NT |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
After running the installer including the brook gpu AstroPulse version I get the following start up message. I tried using my previous app_info.xml file (had been using the brook version previously) but it still gives the same messages. Not sure if this is an SETI or Lunatics problem. I have just disabled GPU processing for now to keep from trashing any more AP tasks. My GPU is a Radeon HD Mobility 3400 First of all unhide your PCs on web preferencies. Check twice brook was selected. send me your app_info in PM. SETI apps news We're not gonna fight them. We're gonna transcend them. |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
SSE2 should go just fine for you. SETI apps news We're not gonna fight them. We're gonna transcend them. |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
Install went the way it is supposed to. Tasks in progess should never be moved between CPU and GPU and between Brook GPU and anything else. Besides that GPU builds are compatible by checkpoints. SETI apps news We're not gonna fight them. We're gonna transcend them. |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
Install went the way it is supposed to. More probably reason in these lines: 12:06:57 (320): Can't acquire lockfile (32) - waiting 35s task was not stopped with BOINC shutdown. Time to time BOINC can't issue correct command for app to quit. So it's worth to check if all apps really stopped after BOINC shutdown. SETI apps news We're not gonna fight them. We're gonna transcend them. |
Wiggo Send message Joined: 24 Jan 00 Posts: 34841 Credit: 261,360,520 RAC: 489 |
Which way would be the 'better' way for 2 WUs/GPU? The app_config.xml is fine so long as you use BOINC V7, but seeing as the computers are hidden and BOINC V6 maybe used then only the app_info.xml is the only way to go. Cheers. |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
In short - yes. Tested om GTX295, GT9400, GSO9600... so, conclusion: CUDA23 is the best choice for pre-FERMI. But your particular host could be an exclusion. Always can be exclusions. SETI apps news We're not gonna fight them. We're gonna transcend them. |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
Just go to AMD forums and say big "thank you" for their programming tools quality. We use what we have. And regarding OpenCL MB - not so bad as you think. Regarding 50% speed loss - very probably before you used app compiled with ICC+ IPP with my mods for better performance on AMD. Look, ICC is Intel tool, IPP is Intel tool again (funny, right?). So, go to AMD forum again and add another "Thank you" for their programming tools quality. SETI apps news We're not gonna fight them. We're gonna transcend them. |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
I have question not shore if you have already been asked but anyway You can freely redistribute as long as you keeping original content intact. SETI apps news We're not gonna fight them. We're gonna transcend them. |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
This just means that FFTW planning routine tested you CPU and decided that SSE2 is the best. This just concurs with our own point to drop SSE3: SSE2 performs reasonably well on SSE3 hosts. Moreover, some old AMD Athlon64 CPUs like Venice have quite poor SSE3 implementation. Even older x64 SSE2 apps beat same but SSE3 app on those CPUs, tested personally. In general - support of some SIMD level means nothing for performance. SSE3 IA can be supported but SSE3 instruction can take so many CPU cycles that better to avoid its usage for performance reasons. SETI apps news We're not gonna fight them. We're gonna transcend them. |
Keith White Send message Joined: 29 May 99 Posts: 392 Credit: 13,035,233 RAC: 22 |
Heh, this 'poor AMD' thing comes up every time there's some release or another. Guess it's easier to see the wood for the trees having stepped back from CPU development myself for a while. Well thanks for explaining it. "Life is just nature's way of keeping meat fresh." - The Doctor |
Keith White Send message Joined: 29 May 99 Posts: 392 Credit: 13,035,233 RAC: 22 |
When William suggested than an SSE3 offering was possible I was just pointing out that there was a specific AMD SSE3 MB app. BTW, thank you for that. Didn't Intel get into a bit of PR trouble over intentional inferior performance on AMD cpus with ICC and IPP a few years back? Nevermind. I was just a bit tweaked when someone simply waved off SSE3 when we (AMD K10 users) had an excellent one once. Seeing how many of the super crunchers who helped test during the V7 beta are overwhelmingly Intel/Cuda, I just wanted to stand up and remind everyone that not all crunchers are Intel/Cuda. Thank you again Raistmer for your hard work in making these apps possible. I do appreciate it even though I sound like a whinny poster more often than not. "Life is just nature's way of keeping meat fresh." - The Doctor |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
LoL, whinning is Ok, being properly targeted. I practice it too time to time ;D Regarding Intel's "black PR" - yes. Hence those mods - I corrected IPP routines selection. ICC/IPP picked up slower versions for AMD than it could. But funny part is: ICC+IPP still the best/fastest for AMD. Not AMD own tools, but Intel's... It tells a lot IMHO. And again, to have SSE3 doesn't mean to have faster app. Actually, you will have ability to test by yourself and tell us. Joe's all builds will be released as separate packs soon (including SSE3 dropped from installer for simlicity). EDIT: we don't forget AMD nethertheless. Just look on my own fleet ;) SETI apps news We're not gonna fight them. We're gonna transcend them. |
Grant (SSSF) Send message Joined: 19 Aug 99 Posts: 13746 Credit: 208,696,464 RAC: 304 |
My Q6600 Quad cpu is knocking out V7 workunits in 3-1/2 hours, is this about right? My E6600 (since installing Lunatics) knocked the last one over in 1hr 23min. The next one is a VLAR and will probably take over 4.5 hours (before Lunatics it was over 7 with v7). Not sure what the eventual times will be as the estimates are still all over the place, not even close to settling down. GPU estimates are even worse. Grant Darwin NT |
Lazydude Send message Joined: 17 Jan 01 Posts: 45 Credit: 96,158,001 RAC: 136 |
>>>> My Q6600 Quad cpu is knocking out V7 workunits in 3-1/2 hours, is this about right? My Q6600 is also take that amount of time, so i think we are equal .. |
Sutaru Tsureku Send message Joined: 6 Apr 07 Posts: 7105 Credit: 147,663,825 RAC: 5 |
Philip J. Fry wrote: I could use still CPU r557 of APv6 or I must use now the CPU r1797 app, because the app is 'better' for the results/science? It's possible to use still r557? Or this app is outdated and make now wrong results? I D/Led AP6_win_x86_SSE_CPU_r1797.exe separately from Lunatics site, there is an AstroPulse_CPU_ReadMe.txt file included: AstroPulse CPU application currently available in SSE edition. It's intended to process SETI@home AstroPulse v6 tasks. Source code repository: https://setisvn.ssl.berkeley.edu/svn/branches/sah_v7_opt Build from SVN revision: 1797 Date of revision commit: 2013/03/30 16:42:32 Available command line switches: -v N :sets level of verbosity of app. N - integer number. So I just write in ap_cmdline_win_x86_SSE_CPU.txt file: -v x .. and this value is used then for what and how I find the correct value for my system? Thanks. * Best regards! :-) * Philip J. Fry, team seti.international founder. * Optimize your PC for higher RAC. * SETI@home needs your help. * |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14653 Credit: 200,643,578 RAC: 874 |
"verbosity" (ausführlichkeit, according to Google translate) just means how much text is written into the stderr_txt file. It's a debugging tool, useful to the programmers in testing, but it shouldn't be needed in normal running. Leave it set at the default level unless you are trying to track down a specific problem: it'll slow your machine down (by a tiny, imperceptible amount), and all that text gets stored on the project servers, too, which isn't a good idea. |
__W__ Send message Joined: 28 Mar 09 Posts: 116 Credit: 5,943,642 RAC: 0 |
Philip J. Fry wrote: I could use still CPU r557 of APv6 or I must use now the CPU r1797 app, because the app is 'better' for the results/science?No problems runing the r557 here. I switched back manualy from the r1797 to the r557 because the r1797 stops chrunching the WU after 50-60% (~6-8 hours on my little C2D T7600) without any reason. In process explorer i can see that the process is not frozen but it dosen't continue the WU ??? After going back to r557 the WU continues, finish and got validated without problems. For performance the r557 seems to be a little bit quicker - ~2-3% ;-) , but i only tryed 2 WUs. __W__ _______________________________________________________________________________ |
William Send message Joined: 14 Feb 13 Posts: 2037 Credit: 17,689,662 RAC: 0 |
Philip J. Fry wrote:I could use still CPU r557 of APv6 or I must use now the CPU r1797 app, because the app is 'better' for the results/science?No problems runing the r557 here. you can continue to use r557, but we can't put it into the installer any more (or distribute in general). It's Jason's build using statically linked libraries - those are traditionally faster than the dynamically linked ones (i.e. Raistmer's r555 and r1797) You'll have to ask Raistmer what kind of improvements he did inbetween. A person who won't read has no advantage over one who can't read. (Mark Twain) |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.