| Author | Message |
|---|
|
|
|
I was going to post this under another thread in reply to someone's question but the thread got locked just as I was about to post. Below are some instructions I typed up about how to have a combined app_info. Please take note of the disclaimer.
MarkJ
Setting up Seti@home to run cuda and non-cuda apps
You will need a copy of BOINC 6.6.15 (or later). This won't work with earlier versions of BOINC.
Disclaimer:
BOINC 6.6.15 is a Development version and may not function correctly. If you are not comfortable with editing an app_info, using optimised apps and running development versions of BOINC then this is not for you.
BOINC is very unforgiving of an incorrect app_info and usually will delete all tasks if you get it wrong.
Do NOT use Internet Explorer to edit the xml files, it will stuff up your app_info. Use Notepad or another text editor.
Thanks go to Richard Haselgrove and Claggy for ideas in building this app_info.xml file.
Notes:
Upgrade your BOINC client first and get it working before changing anything else.
The app_info.xml below is based on a 32 bit Windows platform. If you are running on another platform you may need to add/amend the <platform_name> tags.
My computers support the SSSE3 instruction set. SSE2, SSE3 or SSE4.1 may be more appropiate for you. You will need to amend the program names as appropiate.
I've assumed that you have your cuda-capable card up and running and have the necessary nvidia drivers (minimum version is 180.48).
Programs needed:
a) Optimised multibeam and optimised Astropulse
AK_v8_win_SSSE3x.exe
ap_5.00r103_SSE3.exe
ap_5.03r112_SSE3.exe
b) Cuda multibeam and support libraries
setiathome_6.08_windows_intelx86__cuda.exe
cudart.dll
cufft.dll
libfftw3f-3-1-1a_upx.dll
1. Download and install BOINC 6.6.15. Get this working before changing anything else.
2. Empty your cache of Seti@home work. This is best achieved by setting the project to No new work and letting it finish off its tasks. Make sure they are all uploaded and reported, there should be none on your tasks list.
3. Download the optimised multibeam and astropulse apps (usually from the lunatics web site) if you don't already have them.
4. Download the cuda multibeam app (from the Seti web site) if you don't already have them. If you run the stock cuda multibeam app then you should already have these in your projects\Setiathome.berkeley.edu folder.
5. Disable network communications in BOINC. Shutdown BOINC. Make sure its shutdown.
6. Browse your client_state.xml file (its in the BOINC data directory) and look for the entry <p_flops>. We need to use this number. Do NOT change this file.
7. Browse the BOINC log file to get the estimated speed of your GPU. This is usually given at the top of the log in Gflops. My 9800GT was estimated at 60Gflops.
8. For each of the apps multiply the p_flops value by the factor below and put this into the appropiate flops entry in the app_info given below. For multibeam 608 you need the estimated Gflops.
Astropulse 500 flops = p_flops x 2.25
Astropulse 503 flops = p_flops x 2.6
Multibeam 603 flops = p_flops x 1.75
Multibeam 608 flops = Est.Gflops x 0.2 (eg 60,000,000,000 x 0.2 = 12,000,000,000)
9. Make sure you have all the programs listed above in the projects\Setiathome.berkeley.edu folder. If not copy them there.
10. Save your app_info in the projects\Setiathome.berkeley.edu folder.
11. Start up BOINC. Check the messages tab to see if it lists any [file error] messages. If there are shut BOINC, check you have the correct program names referenced. Go back to step 9.
12. If okay then enable new work for the Seti@home project.
13. Enable network communications again.
14. It should now download work of all types. If not check your Seti@home preferences on the Seti web site, that Astropulse, Astropulse_v5 and "Use GPU if available" are all ticked. If you have a slower computer you may not get astropulse work units anyway.
<app_info>
<app>
<name>astropulse</name>
</app>
<file_info>
<name>ap_5.00r103_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse</app_name>
<version_num>500</version_num>
<flops>5306156897</flops>
<file_ref>
<file_name>ap_5.00r103_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<flops>6131559081</flops>
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8_win_SSSE3x.exe</name>
<executable/>
</file_info>
<file_info>
<name>setiathome_6.08_windows_intelx86__cuda.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx86</platform>
<flops>4127010920</flops>
<file_ref>
<file_name>AK_v8_win_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.127970</avg_ncpus>
<max_ncpus>0.127970</max_ncpus>
<flops>12000000000</flops>
<plan_class>cuda</plan_class>
<file_ref>
<file_name>setiathome_6.08_windows_intelx86__cuda.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>
</app_info>
____________
BOINC blog
 |
|
|
|
|
|
This is great info. I nominate this thread to be made sticky. |
|
|
|
|
This is great info. I nominate this thread to be made sticky.
I'll second that motion.
____________
PROUD MEMBER OF Team Starfire World BOINC |
|
|
|
|
|
I'm not so sure that running the development app is such a good idea for the general public. I'd say yes to sticky if the 6.6.15 were the standard. Currently 6.4.7 is. Mention of which OS this has worked on would be great as well...
____________
come fly with us at TSWB. Turn off ASTROPULSE HERE
 |
|
|
|
|
|
Ok, postpone my nomination to when 6.6.15 (or whichever becomes the stable version) is available for general release. :) |
|
|
|
|
I'm not so sure that running the development app is such a good idea for the general public. I'd say yes to sticky if the 6.6.15 were the standard. Currently 6.4.7 is. Mention of which OS this has worked on would be great as well...
I made it very clear that it relates to a Development version in the disclaimer. While it would be nice if it worked under earlier versions of BOINC, unfortunately it doesn't.
Re: The OS, It says at the top. Windows 32 bit. To be more precise XP Pro with SP3.
____________
BOINC blog
|
|
|
|
|
This is great info. I nominate this thread to be made sticky.
I'll second that motion.
Sorry guys-moderator have been repeatedly asked by users to keep the stickies to a minimum wherever possible.
____________
 Play Fallen Sword! |
|
|
|
|
|
<p_fpops>? |
|
|
|
|
<p_fpops>?
"Floating Point Operations per Second" - a measure of speed (CPU in this case).
You can copy the value from the line with this tag in the first block of data in client_state.xml: alternatively, the same figure is shown on the 'host details' page on this website, in the line "Measured floating point speed 1830.43 million ops/sec".
Notice that the speed shown on the website is in millions of <p_fpops>: you need to multiply those millions back in before using the number in Mark's formula. |
|
|
|
|
<p_fpops>?
"Floating Point Operations per Second" - a measure of speed (CPU in this case).
You can copy the value from the line with this tag in the first block of data in client_state.xml: alternatively, the same figure is shown on the 'host details' page on this website, in the line "Measured floating point speed 1830.43 million ops/sec".
Notice that the speed shown on the website is in millions of <p_fpops>: you need to multiply those millions back in before using the number in Mark's formula.
I actually cut it from client_state and pasted it into calculator under windows and then did the multiplication. Less chance of errors that way :)
You'll note that I dropped off the decimals in the app_info provided. I figure a half a fpop isn't going to make any difference.
____________
BOINC blog
|
|
|
|
|
|
Taken from the app_info.xml posted:
<platform>windows_intelx86</platform>
Does this actually do anything? And should it be changed when running on the 64-bit version of Windows, or does it only have to be changed when running on Linux or OS X?
I'm asking because I feel that after building up my courage for a week I am now ready to adopt 6.6.14 (or .15) on my rig :-) But it runs under x64, not x86.
Another question: if I don't want to run multibeam on the cpu, do I just remove the part describing the 6.03 application (ak v8, that is) or are more drastic measures necessary?
Regards,
John.
|
|
|
Fred W Volunteer tester
Send message
Joined: Jun 13 99
Posts: 2175
Credit: 5,926,236
RAC: 19,577
|
Taken from the app_info.xml posted:
<platform>windows_intelx86</platform>
Does this actually do anything? And should it be changed when running on the 64-bit version of Windows, or does it only have to be changed when running on Linux or OS X?
I'm asking because I feel that after building up my courage for a week I am now ready to adopt 6.6.14 (or .15) on my rig :-) But it runs under x64, not x86.
Another question: if I don't want to run multibeam on the cpu, do I just remove the part describing the 6.03 application (ak v8, that is) or are more drastic measures necessary?
Regards,
John.
The equivalent line from my installation:
<platform>windows_x86_64</platform>
Please do change it - I trashed a lot of WU's because I forgot about this wrinkle :-(
With 6.6.14 and .15 you won't get any 6.03's anyway even if you leave the AK_v8 line in there. It is all branded as MultiBeam so the server uses the highest version number (i.e. the 6.08) and you only get CUDA branded MB.
F.
____________
 |
|
|
|
|
With 6.6.14 and .15 you won't get any 6.03's anyway even if you leave the AK_v8 line in there. It is all branded as MultiBeam so the server uses the highest version number (i.e. the 6.08) and you only get CUDA branded MB.
F.
Not true. With 6.6.14 and above, you can receive (I have received) 603 work for AK_v8 as part of a standard work fetch from the project, as well as 608 CUDA work. You can also (and I have done this as a test, but I don't recommend it) ask for and receive AK_v8 work branded as 608, and CUDA work branded as 608, all in the same configuration.
The point is, the <plan_class>cuda</plan_class> line (in the 608 section in MarkJ's example) now serves to differentiate that section from the 603 section: MultiBeam and MultiBeam CUDA, although being identical tasks and datafiles, can now be tracked separately through the system and requested individually.
That's why v6.6.14 and above is such a big upgrade, and has to be handled with such care.
(And Fred - it's also why I'm looking forward with such anticipation to the 608 --> 603 rebranding script for VLAR. One tester, at your service whenever called upon!) |
|
|
Fred WVolunteer tester
Send message
Joined: Jun 13 99
Posts: 2175
Credit: 5,926,236
RAC: 19,577
|
With 6.6.14 and .15 you won't get any 6.03's anyway even if you leave the AK_v8 line in there. It is all branded as MultiBeam so the server uses the highest version number (i.e. the 6.08) and you only get CUDA branded MB.
F.
Not true. With 6.6.14 and above, you can receive (I have received) 603 work for AK_v8 as part of a standard work fetch from the project, as well as 608 CUDA work. You can also (and I have done this as a test, but I don't recommend it) ask for and receive AK_v8 work branded as 608, and CUDA work branded as 608, all in the same configuration.
The point is, the <plan_class>cuda</plan_class> line (in the 608 section in MarkJ's example) now serves to differentiate that section from the 603 section: MultiBeam and MultiBeam CUDA, although being identical tasks and datafiles, can now be tracked separately through the system and requested individually.
That's why v6.6.14 and above is such a big upgrade, and has to be handled with such care.
(And Fred - it's also why I'm looking forward with such anticipation to the 608 --> 603 rebranding script for VLAR. One tester, at your service whenever called upon!)
My apologies, then, for providing duff info. I was going by my own experience which is that I have never received a 603 WU since I fired up my graphics card. I bow to Richard's differing experience and assume I was just "unlucky" - but then I prefer to leave as much CPU time for AP as possible anyway (apart from the darned VLARs); seems much cleaner that way.
(And Richard - almost there. Just checking the automation on Vista and XP. Think on this, though. With (6.6.x) Boinc's propensity to process CUDA WU's in deadline order, a run of the script to re-brand the VLARs in the cache followed by a work fetch often brings down more VLAR's that have earlier deadlines than the existing non-VLARs so whatever the size of cache some get crunched on the GPU anyway. Another effect of the same "bug" that I noticed immediately following Tuesday's outage was that CUDAs were downloaded with progressively closer deadlines so that I eventually had 8 partially crunched "waiting to run" which had been usurped be those that came after.)
F.
____________
|
|
|
|
|
... I have never received a 603 WU since I fired up my graphics card ...
(And Richard - almost there. Just checking the automation on Vista and XP. Think on this, though. With (6.6.x) Boinc's propensity to process CUDA WU's in deadline order, a run of the script to re-brand the VLARs in the cache followed by a work fetch often brings down more VLAR's that have earlier deadlines than the existing non-VLARs so whatever the size of cache some get crunched on the GPU anyway. Another effect of the same "bug" that I noticed immediately following Tuesday's outage was that CUDAs were downloaded with progressively closer deadlines so that I eventually had 8 partially crunched "waiting to run" which had been usurped be those that came after.)
F.
I only got the 603s with deliberate testing (by disabling AP allocation). But I got 'em.
re VLARs - what threshhold are you using for defining VLAR? I think you can cap it at 0.05, which is the definition of a 'true' VLAR. I believe Raistmer took the dividing line a bit higher for safety - something like 0.14
If you take the 0.05 line, then all VLARs will have exactly the same deadline interval after issue by the scheduler, which means that a 'new' VLAR will never queue-jump another VLAR: but you're right, a new VLAR could easily jump the next available non-VLAR. |
|
|
|
|
|
[quoteThe equivalent line from my installation:
<platform>windows_x86_64</platform>
Please do change it - I trashed a lot of WU's because I forgot about this wrinkle :-(
[/quote]
Thanks Fred, I will use that one as well, then.
The funny thing is: I'm at this moment running 6.6.15 with my 'old' app_info.xml that I had for 6.4.7. It has optimized versions of old and new astropulse and the stock cuda application in it. None of the fancy stuff that the proposed app_info has.
I upgraded the old boinc by installing 6.6.15 right over it, changing nothing else (well, I removed my cc_config because it had the n+1 cpus in it). When I started the new boincmanager it picked up the old astropulse work flawlessly and started asking for (and got, hooray) new cuda work. It worked right out of the box, somewhat to my surprise.
I'm bound to start tinkering with it, though. I'll probably end up using a copy of the app_info provided by MarkJ. Major reason to do so is that I also feel the need to do something about those annoying vlar cuda's, so I'll have a description of akv8 ready to get those things offloaded to the cpu when your fix is ready :-)
Regards,
John.
|
|
|
|
|
The equivalent line from my installation:
<platform>windows_x86_64</platform>
Please do change it - I trashed a lot of WU's because I forgot about this wrinkle :-(
I had the _x86_64 at both occurrences of <platform> but it trashed all my cuda units immediately on startup. I got an error message indicating that there was no version info for the 64bit cuda executable (?)
20-Mar-2009 10:10:22 [SETI@home] [error] No app version for result: windows_x86_64 608 cuda
20-Mar-2009 10:10:22 [SETI@home] [error] No app version for result: windows_x86_64 608 cuda
etc. It seems to think that I want my 608 to be handled by a 64-bit application, at least that's what I make of this message ....
I then changed the <platform> in the cuda section back to windows_x86. Seems to work, at least I get no error messages and it is asking for work (but not getting any, according to the message on the home page the science database crashed, no work available).
Does this make sense? My ak_v8 is a 64-bit application and uses the x86_64 platform description, my cuda executable is a 32-bit application (I'm not aware of the existence of a 64-bit cuda executable?) and uses the x86 description. Is this as it is supposed to be or am I just screwing things up, as usual :-)
Regards,
John.
|
|
|
Fred WVolunteer tester
Send message
Joined: Jun 13 99
Posts: 2175
Credit: 5,926,236
RAC: 19,577
|
The equivalent line from my installation:
<platform>windows_x86_64</platform>
Please do change it - I trashed a lot of WU's because I forgot about this wrinkle :-(
I had the _x86_64 at both occurrences of <platform> but it trashed all my cuda units immediately on startup. I got an error message indicating that there was no version info for the 64bit cuda executable (?)
20-Mar-2009 10:10:22 [SETI@home] [error] No app version for result: windows_x86_64 608 cuda
20-Mar-2009 10:10:22 [SETI@home] [error] No app version for result: windows_x86_64 608 cuda
etc. It seems to think that I want my 608 to be handled by a 64-bit application, at least that's what I make of this message ....
I then changed the <platform> in the cuda section back to windows_x86. Seems to work, at least I get no error messages and it is asking for work (but not getting any, according to the message on the home page the science database crashed, no work available).
Does this make sense? My ak_v8 is a 64-bit application and uses the x86_64 platform description, my cuda executable is a 32-bit application (I'm not aware of the existence of a 64-bit cuda executable?) and uses the x86 description. Is this as it is supposed to be or am I just screwing things up, as usual :-)
Regards,
John.
After I had trashed my cache, I decided that the harm had already been done and left the platform description at x86_64 throughout the app_info. That's how it has been running quite happily for over a week now.
F.
____________
|
|
|
|
|
The equivalent line from my installation:
<platform>windows_x86_64</platform>
Please do change it - I trashed a lot of WU's because I forgot about this wrinkle :-(
I had the _x86_64 at both occurrences of <platform> but it trashed all my cuda units immediately on startup. I got an error message indicating that there was no version info for the 64bit cuda executable (?)
20-Mar-2009 10:10:22 [SETI@home] [error] No app version for result: windows_x86_64 608 cuda
20-Mar-2009 10:10:22 [SETI@home] [error] No app version for result: windows_x86_64 608 cuda
etc. It seems to think that I want my 608 to be handled by a 64-bit application, at least that's what I make of this message ....
I then changed the <platform> in the cuda section back to windows_x86. Seems to work, at least I get no error messages and it is asking for work (but not getting any, according to the message on the home page the science database crashed, no work available).
Does this make sense? My ak_v8 is a 64-bit application and uses the x86_64 platform description, my cuda executable is a 32-bit application (I'm not aware of the existence of a 64-bit cuda executable?) and uses the x86 description. Is this as it is supposed to be or am I just screwing things up, as usual :-)
Regards,
John.
After I had trashed my cache, I decided that the harm had already been done and left the platform description at x86_64 throughout the app_info. That's how it has been running quite happily for over a week now.
F.
I've left mine as windows_x86, lost several caches worth before the new scheduler was installed on Seti Main, while i tried to get GPU requests to work,
and haven't run the cache down yet to try again.
Claggy |
|
|
|
|
|
Well this week's outage opened a good opportunity to empty some queues and install 6.6.17. I still had some AP V5s (and WCG work which hopefully won't care). After the install the APs are estimated to finish in about 3 hours (I wish!) - I guess the estimates will equalise over time (or I've cocked up the flop values in the APP_INFO). Without MB work available I downloaded some GPUGRID work and all seems to re running happily (AP WCG and GPUGRID).
____________
|
|
|
|
|
Not true. With 6.6.14 and above, you can receive (I have received) 603 work for AK_v8 as part of a standard work fetch from the project, as well as 608 CUDA work. You can also (and I have done this as a test, but I don't recommend it) ask for and receive AK_v8 work branded as 608, and CUDA work branded as 608, all in the same configuration.
The point is, the <plan_class>cuda</plan_class> line (in the 608 section in MarkJ's example) now serves to differentiate that section from the 603 section: MultiBeam and MultiBeam CUDA, although being identical tasks and datafiles, can now be tracked separately through the system and requested individually.
(And Fred - it's also why I'm looking forward with such anticipation to the 608 --> 603 rebranding script for VLAR. One tester, at your service whenever called upon!)
Is it possible to have a setup where MB WUs are only fetched for CUDA processing, but AK V8 is still defined? The reason for the question is that I'd prefer to do MBs only on CUDA and leave the CPU free for AP work. However Fred's 603 rebranding script will require the 603 AK V8 entry in app-info to process the vlars, in which case CPU-based 603 MB work might be fetched.
____________
|
|
|
|
|
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
what is coproc count for?
____________
 |
|
|
|
|
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
what is coproc count for?
As far as I understand its the number of coproc's it needs to process a single work unit. So in this case 1 wu needs 1 co-processor (or gpu) to run. If you have more co-processors then you can run more wu at the same time.
____________
BOINC blog
|
|
|
|
|
|
Can't find the boinc log with G flops on it. also don't have cuda 608exe. Will cuda mod exe. work?
____________
  |
|
|
|
|
Can't find the boinc log with G flops on it. also don't have cuda 608exe. Will cuda mod exe. work?
If you want to use Raistmer's apps, use the 'MB_6.08_mod_CUDA_V10.exe' from his V11 download, instead of the stock app,
just add the file name to the app_info, and drop the file into your seti folder.
Claggy |
|
|
|
|
Can't find the boinc log with G flops on it. also don't have cuda 608exe. Will cuda mod exe. work?
In the boinc log (just click on the messages tab in BOINCmgr) it will be near the top, along with the device driver version and graphics card details. Don't forget all the extra zeroes seeing as its in gigaflops.
____________
BOINC blog
|
|
|
RaistmerVolunteer developer
Volunteer tester
Send message
Joined: Jun 16 01
Posts: 1016
Credit: 5,954,006
RAC: 12,572
|
Can't find the boinc log with G flops on it. also don't have cuda 608exe. Will cuda mod exe. work?
Yes, it will.
YOu need either rename it to match stock app name, or do correct app_info file.
|
|
|
|
|
|
what is wrong with my app_info.xml file, I replaced AK_v8_win_SSSE3x.exe with AK_v8b_win_x64_SSSE3x_GPU_CPU_team_V10.exe. when ever bonic tries to execute a regular "setiathome_enhanced 6.03" (non cuda) it the application AK_v8b... crashes with a windows error and the returns the result as an error of coarse. cpu is a Q9450 and is ssse3 and sse4.1 compatible.
is the 6.03 wu not compatilble with AK_v8b_win_x64_SSSE3x_GPU_CPU_team_V10.exe or is the problem with how the wu is passed off to the application?
or could it be because i used the 64 bit app???
<app_info>
<app>
<name>astropulse</name>
</app>
<file_info>
<name>ap_5.00r103_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse</app_name>
<version_num>500</version_num>
<flops>8122702500</flops>
<file_ref>
<file_name>ap_5.00r103_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<flops>18276080625</flops>
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8b_win_x64_SSSE3x_GPU_CPU_team_V10.exe</name>
<executable/>
</file_info>
<file_info>
<name>MB_6.08_mod_CUDA_V10.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx86</platform>
<flops>41121181406</flops>
<file_ref>
<file_name>AK_v8b_win_x64_SSSE3x_GPU_CPU_team_V10.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.127970</avg_ncpus>
<max_ncpus>0.127970</max_ncpus>
<flops>30000000000</flops>
<plan_class>cuda</plan_class>
<file_ref>
<file_name>MB_6.08_mod_CUDA_V10.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>
</app_info>
____________
|
|
|
|
|
|
I've one GTX295 (counted as 2 CUDAs) @106GFLOPS each and 8600GTS @20GLOPS so I have total 3 CPU, should I use GTX295's GLOPS value, 8600's value or average (106+106+20)/3=77.33GLOPS in the calculation?
Appreciate any advise. Many thanks in advance |
|
|
|
|
I've one GTX295 (counted as 2 CUDAs) @106GFLOPS each and 8600GTS @20GLOPS so I have total 3 CPU, should I use GTX295's GLOPS value, 8600's value or average (106+106+20)/3=77.33GLOPS in the calculation?
Appreciate any advise. Many thanks in advance
Depends what you want to achieve, and how you want BOINC to work for you.
The idea of the FLOPS calculations in this thread was to compensate for the different efficiencies and estimates of the four different applications in the thread title. If you get the ratio right, there will be no systematic variation in the DCF (Duration Correction Factor) when a task finishes - because you have already applied your own correction factor.
In your situation, you have five correction factors to contend with (the final app being split into MB/608/GTX295 and MB/608/8600GTS), and only four FLOPS figures to juggle with. With a speed diffence of more than 5::1 between your CUDA cards, the sawteeth on your DCF graph will be sharp enough to cut down a rainforest.
The BOINC approach would be safety-first: plug in the value of your slowest card. Then, according to BOINC, you should never download too much work and risk missing deadlines. But that doesn't bear inspection: in between the (relatively rare) task completions by your 8600GTS card, DCF will be driven rapidly downwards by the (frequent) completions on the GTX295. Because, in current versions of BOINC, you only have a single DCF, and it controls the CPU apps as well, that could lead to you downloading an excess of AP tasks that you subsequently have difficulty completing on time.
So, thinking about it (and I'm making this up as I go along), I suggest you put the speed of the fastest card into Mark's formula. Every time the 8600GTS finishes a task, work fetch will be inhibited for a while (and, depending on the size of your cache, you may see a burst of EDF ('high priority') running on the CPU), but you should never be at risk of missing a deadline. |
|
|
|
|
|
I had my flops wrong for 503 (bad math)my DCF was at 2hrs. and I got mass 503s , changed it and it's back about right now.Worked out because this was just before the shut down.Now have lots of work but no 608s poor cuda. |
|
|
|
|
what is wrong with my app_info.xml file, I replaced AK_v8_win_SSSE3x.exe with AK_v8b_win_x64_SSSE3x_GPU_CPU_team_V10.exe. when ever bonic tries to execute a regular "setiathome_enhanced 6.03" (non cuda) it the application AK_v8b... crashes with a windows error and the returns the result as an error of coarse. cpu is a Q9450 and is ssse3 and sse4.1 compatible.
is the 6.03 wu not compatilble with AK_v8b_win_x64_SSSE3x_GPU_CPU_team_V10.exe or is the problem with how the wu is passed off to the application?
or could it be because i used the 64 bit app???
<app_info>
<app>
<name>astropulse</name>
</app>
<file_info>
<name>ap_5.00r103_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse</app_name>
<version_num>500</version_num>
<flops>8122702500</flops>
<file_ref>
<file_name>ap_5.00r103_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<flops>18276080625</flops>
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8b_win_x64_SSSE3x_GPU_CPU_team_V10.exe</name>
<executable/>
</file_info>
<file_info>
<name>MB_6.08_mod_CUDA_V10.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx86</platform>
<flops>41121181406</flops>
<file_ref>
<file_name>AK_v8b_win_x64_SSSE3x_GPU_CPU_team_V10.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.127970</avg_ncpus>
<max_ncpus>0.127970</max_ncpus>
<flops>30000000000</flops>
<plan_class>cuda</plan_class>
<file_ref>
<file_name>MB_6.08_mod_CUDA_V10.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>
</app_info>
You have the 64 bit app and the platform is saying you are a 32 bit one. Further up in the thread there is discussion about the platform to use.
____________
BOINC blog
|
|
|
|
|
|
Does the new 6.6.17 client "Elapsed Time" counter now work properly with CUDA WU's. I've managed to get it working and I noticed that the counter is contstantly counting. My GPU thermals have gone up so to me it looks like its running ok. Anyone else notice this?
Vager
____________
 |
|
|
|
|
|
Running 6.6.17 with MJ apfo just got some 608s and running fine 4 503s on cpu 1 608 on gpu.! cool no baby sitting. was waiting to get some mbs to see it work, and it does. Even though I screwed up on my 503 flops and got too many 503s ,all running high priority.did some math and aborted about 50 of them ,but even though my cpu has too many tasks 6.6.17 still dled cuda tasks so I'm a happy cruncher. I thought my rac at 8550 was pretty good but now with the gpu working..well who knows????????????????????
____________
|
|
|
|
|
|
hey guys.
one question/request
who can provide me a working app_info (using optimized apps) file just for astropulse and mb on a machine wich has no cuda capable card.
intented is the use of boin ver 6.6.18 or above.
thx in advance |
|
|
RaistmerVolunteer developer
Volunteer tester
Send message
Joined: Jun 16 01
Posts: 1016
Credit: 5,954,006
RAC: 12,572
|
hey guys.
one question/request
who can provide me a working app_info (using optimized apps) file just for astropulse and mb on a machine wich has no cuda capable card.
intented is the use of boin ver 6.6.18 or above.
thx in advance
It's supplied with AP/MB combos, nothing new for 6.6.18 specifically needed for non-CUDA host IMHO.
|
|
|
|
|
|
ok thx for the reply raistmer. apreciated |
|
|
|
|
|
This procedure worked great. Two comments and one observation:
Comment 1: In step #6, I think you mean p_fpops instead of p_flops.?.
Comment 2: It would be helpful if the instructions included multiple CUDA cards. I assumed that the number of CUDA needed to be 2 (instead of 1). But, I was not sure how to fill out the multibeam 608 GFlops rating. I averaged the two cards GFlop ratings.
Observation: BOINC version 6.6.20 did not take full advantage of both CUDA cards. In version 6.4.7, a single CPU core would keep both CUDA cards busy. Now, the second card is listed as "waiting to run".
|
|
|
|
|
This procedure worked great. Two comments and one observation:
Comment 1: In step #6, I think you mean p_fpops instead of p_flops.?.
Comment 2: It would be helpful if the instructions included multiple CUDA cards. I assumed that the number of CUDA needed to be 2 (instead of 1). But, I was not sure how to fill out the multibeam 608 GFlops rating. I averaged the two cards GFlop ratings.
Observation: BOINC version 6.6.20 did not take full advantage of both CUDA cards. In version 6.4.7, a single CPU core would keep both CUDA cards busy. Now, the second card is listed as "waiting to run".
Richard Haselgrove answered the a question about Multiple Cuda cards flops values earlier in this thread,
Try changing the CUDA number back to 1, MarkJ seems to think it's the number of coproc's it needs to process a single work unit, see earlier in this thread.
Have you removed any <ncpus> entries from your cc_config?, Boinc 6.6.x doesn't need it anymore, it should be able to tell how many GPU's you have without using any work arounds.
Claggy |
|
|
|
|
This procedure worked great. Two comments and one observation:
Comment 1: In step #6, I think you mean p_fpops instead of p_flops.?.
Comment 2: It would be helpful if the instructions included multiple CUDA cards. I assumed that the number of CUDA needed to be 2 (instead of 1). But, I was not sure how to fill out the multibeam 608 GFlops rating. I averaged the two cards GFlop ratings.
Observation: BOINC version 6.6.20 did not take full advantage of both CUDA cards. In version 6.4.7, a single CPU core would keep both CUDA cards busy. Now, the second card is listed as "waiting to run".
Agree with comment 1, it is now <p_fpops>. Not sure if it was a typo or the older version (6.6.15 when I wrote it).
BOINC should see all the cuda-capable cards and they should work without any additional changes. It does have a problem when you mix different cards with different f_pops as you can only give BOINC one value.
As Claggy mentioned if you have an <ncpus> statement in your cc_config file you should remove it as its no longer required under the 6.6 versions of BOINC.
Also as Claggy mentioned the coproc <count> is used to tell BOINC how many cuda devices are needed to run a single wu, so this should remain at 1.
____________
BOINC blog
|
|
|
|
|
...It does have a problem when you mix different cards with different f_pops as you can only give BOINC one value.
MarkJ, could you elaborate a little on that statement, please? I have a system I am running the cache down on to install your optimized apps, and have 3 EVGA 8400GS cards, and one EVGA GTX 260, so I am a little concerned about issues I may run into after reading your above comment. Thanks much!
____________
 |
|
|
|
|
...It does have a problem when you mix different cards with different f_pops as you can only give BOINC one value.
MarkJ, could you elaborate a little on that statement, please? I have a system I am running the cache down on to install your optimized apps, and have 3 EVGA 8400GS cards, and one EVGA GTX 260, so I am a little concerned about issues I may run into after reading your above comment. Thanks much!
89 + 5 + 5 + 5 GFLOPS = 104 / 4 = 26 GFLOPS average. That's the raw figure you should base the app_info.xml <flops> in the CUDA app section on. The Scheduler will try to give you enough CUDA work to keep those 4 GPUs busy, the 260 will do a lot more of it than the PCI 8400GS cards. Joe |
|
|
|
|
...It does have a problem when you mix different cards with different f_pops as you can only give BOINC one value.
MarkJ, could you elaborate a little on that statement, please? I have a system I am running the cache down on to install your optimized apps, and have 3 EVGA 8400GS cards, and one EVGA GTX 260, so I am a little concerned about issues I may run into after reading your above comment. Thanks much!
The problem is the cards are capable of different speeds. The number that we are giving BOINC in the app_info is used so it can figure out how much work you would normally be able to process, just for Seti cuda. This in turn effects how much work BOINC will download.
You could take the approach Josef has suggested and average them out. This is probably the best approach for what you are doing.
If you had access to another machine perhaps it would be wiser to put the 3 8400GS's in one and the GTX260 in another. This way you could have different <f_pops> values for each machine. It would also save stressing one power supply by running 4 cards off it.
____________
BOINC blog
|
|
|
|
|
|
Well, I could move it to another board, as these are all just boards sitting out on the desk, they aren't actually in cases. I am trying to get my fastest non-I7 system loaded up with cards to see how well it will do, it has one PCI-E slot and 3 PCI slots, along with a couple shortie (I think PCI-E 1x?) slots, and would like to see how much one machine can handle. I am running a PCP&C 1000w power supply, so that shouldn't be a problem, the PCI cards don't even have external power connectors, they're running off the PCI bus. Do you know if anyone makes a shortie PCI-E single slot video card? It would be interesting to see if I could run 6 video cards in one machine... :D
____________
|
|
|
|
|
Do you know if anyone makes a shortie PCI-E single slot video card?
The only ones at Newegg are Radeons, so no help there.
____________
 |
|
|
|
|
|
What am I doing wrong?
I have an EMachines Celeron C2D 2.0 ssse3 capable with an 8500GT 512MB graphics card estimated at 5Gflops. I have BM 6.6.20.
My FPOPS are 1864335675.
I have put the necessary files in my setiathome folder and did the math for each type of workunits.I ran my cache down to zero but when I put the app_info file in and restarted BM it erases the setiathome_6.08_windows_intelx86__cuda.exe file and gives the message url cannot be found to download it again thus causing all 6.08 WUs to error out in downloading. I copied MarkJ's app_info exactly, changed the numbers to my specs, and placed it in my setiathome folder.
This is my app_info file:
<app_info>
<app>
<name>astropulse</name>
</app>
<file_info>
<name>ap_5.00r103_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse</app_name>
<version_num>500</version_num>
<flops>4194755270</flops>
<file_ref>
<file_name>ap_5.00r103_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<flops>4847272757</flops>
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8_win_SSSE3x.exe</name>
<executable/>
</file_info>
<file_info>
<name>setiathome_6.08_windows_intelx86__cuda.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx86</platform>
<flops>3269311494</flops>
<file_ref>
<file_name>AK_v8_win_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.127970</avg_ncpus>
<max_ncpus>0.127970</max_ncpus>
<flops>1000000000</flops>
<plan_class>cuda</plan_class>
<file_ref>
<file_name>setiathome_6.08_windows_intelx86__cuda.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>
</app_info>
I have too much work right now to let it run back down so I will have to detach and start all over after I get some recommendations from you guys.
____________
PROUD MEMBER OF Team Starfire World BOINC |
|
|
|
|
|
Just to add a bit more information and to bump this up a little, here is the first few lines from the start of Boinc Manager...
4/6/2009 9:08:47 PM Starting BOINC client version 6.6.20 for windows_intelx86
4/6/2009 9:08:47 PM log flags: task, file_xfer, sched_ops
4/6/2009 9:08:47 PM Libraries: libcurl/7.19.4 OpenSSL/0.9.8j zlib/1.2.3
4/6/2009 9:08:47 PM Data directory: C:\ProgramData\BOINC
4/6/2009 9:08:47 PM Running under account perry
4/6/2009 9:08:47 PM Processor: 2 GenuineIntel Intel(R) Celeron(R) CPU E1400 @ 2.00GHz [x86 Family 6 Model 15 Stepping 13]
4/6/2009 9:08:47 PM Processor features: fpu tsc pae nx sse sse2 pni mmx
4/6/2009 9:08:47 PM OS: Microsoft Windows Vista: Home Premium x86 Editon, Service Pack 1, (06.00.6001.00)
4/6/2009 9:08:47 PM Memory: 3.25 GB physical, 6.73 GB virtual
4/6/2009 9:08:47 PM Disk: 288.09 GB total, 219.87 GB free
4/6/2009 9:08:47 PM Local time is UTC -4 hours
4/6/2009 9:08:47 PM CUDA device: GeForce 8500 GT (driver version 18208, CUDA version 1.1, 512MB, est. 5GFLOPS)
4/6/2009 9:08:47 PM Not using a proxy
4/6/2009 9:08:47 PM SETI@home URL: http://setiathome.berkeley.edu/; Computer ID: 4731257; location: home; project prefs: home
4/6/2009 9:08:47 PM SETI@home General prefs: from SETI@home (last modified 01-Mar-2009 20:10:17)
4/6/2009 9:08:47 PM SETI@home Computer location: home
4/6/2009 9:08:47 PM SETI@home General prefs: no separate prefs for home; using your defaults
4/6/2009 9:08:47 PM Reading preferences override file
4/6/2009 9:08:47 PM Preferences limit memory usage when active to 1663.16MB
4/6/2009 9:08:47 PM Preferences limit memory usage when idle to 2993.69MB
4/6/2009 9:08:47 PM Preferences limit disk usage to 100.00GB
4/6/2009 9:08:47 PM SETI@home Restarting task 09fe09ab.32131.890.11.8.158_1 using setiathome_enhanced version 608
4/6/2009 9:08:47 PM SETI@home Restarting task 09fe09ac.3737.12751.6.8.152_1 using setiathome_enhanced version 603
4/6/2009 9:08:47 PM SETI@home Restarting task 09fe09ac.3737.13160.6.8.240_0 using setiathome_enhanced version 603
____________
PROUD MEMBER OF Team Starfire World BOINC |
|
|
|
|
|
There's no start up message saying this:
05/04/2009 20:57:20 SETI@home Found app_info.xml; using anonymous platform
Check your app_info is actually called app_info.xml
Claggy |
|
|
|
|
|
read your app_info with notepad and make sure it doesnt have any "-" in it.
Make sure the app_info is installed in the correct folder.
____________
come fly with us at TSWB. Turn off ASTROPULSE HERE
|
|
|
|
|
|
There is no app_info file in the start-up because it isn't working with it in there. If I put it back in it will erase the MB_6.08.exe and wipe out all the 6.08 WUs I have. It is running now as stock.
I copied the file to notepad and made sure it was saved as an XML without the .txt sneaking in there at the end.Then I placed it in my setiathome folder where I have placed every other app_info for all the rest of the opt-apps before this one. I have gone over this so many times I'm going creoss-eyed but I can't figure out where the mistake is.
Sorry to sound a bit put out. I appreciate the help but am just frustrated about this not working.
____________
PROUD MEMBER OF Team Starfire World BOINC |
|
|
|
|
There is no app_info file in the start-up because it isn't working with it in there. If I put it back in it will erase the MB_6.08.exe and wipe out all the 6.08 WUs I have. It is running now as stock.
I copied the file to notepad and made sure it was saved as an XML without the .txt sneaking in there at the end.Then I placed it in my setiathome folder where I have placed every other app_info for all the rest of the opt-apps before this one. I have gone over this so many times I'm going creoss-eyed but I can't figure out where the mistake is.
Sorry to sound a bit put out. I appreciate the help but am just frustrated about this not working.
Are you trying to run optimized CPU apps with the stock CUDA app? Or optimized CPU with optimized CUDA?
____________
BOINC FAQ Service
BOINC & Optimized SETI download repository |
|
|
|
|
|
Optimized CPU apps would be fine. My GPU is about as fast as it will get. I don't think there are any optimized GPU apps or at least I don't know of any.
I am running 6.6.20 and am trying to put MarkJ's app_info modified to my system in to the mix.I put all the files (AK V8, AP_5.00, AP_5.03, setiathome_mb6.08, ect.) in my setiathome folder along with this ap_info and fired up Boinc Manager. As soon as it saw the app_info it erased my mb_6.08 file and all the mb 6.08 WU that had started to download. It then told me it couldn't find the url for the setiathome_MB_6.08 file to download it.
____________
PROUD MEMBER OF Team Starfire World BOINC |
|
|
|
|
Optimized CPU apps would be fine. My GPU is about as fast as it will get. I don't think there are any optimized GPU apps or at least I don't know of any.
Raistmer has worked very hard on offering optimized CUDA apps, and I think he releases them paired up with optimized CPU apps.
I am running 6.6.20 and am trying to put MarkJ's app_info modified to my system in to the mix.I put all the files (AK V8, AP_5.00, AP_5.03, setiathome_mb6.08, ect.) in my setiathome folder along with this ap_info and fired up Boinc Manager. As soon as it saw the app_info it erased my mb_6.08 file and all the mb 6.08 WU that had started to download. It then told me it couldn't find the url for the setiathome_MB_6.08 file to download it.
Hmmm... sounds like a problem with the app_info.xml file, though nothing is jumping out at me at the moment.
____________
BOINC FAQ Service
BOINC & Optimized SETI download repository |
|
|
|
|
Optimized CPU apps would be fine. My GPU is about as fast as it will get. I don't think there are any optimized GPU apps or at least I don't know of any.
I am running 6.6.20 and am trying to put MarkJ's app_info modified to my system in to the mix.I put all the files (AK V8, AP_5.00, AP_5.03, setiathome_mb6.08, ect.) in my setiathome folder along with this ap_info and fired up Boinc Manager. As soon as it saw the app_info it erased my mb_6.08 file and all the mb 6.08 WU that had started to download. It then told me it couldn't find the url for the setiathome_MB_6.08 file to download it.
You didn't check what i posted on lunatics earlier did you?
Your error:
<core_client_version>6.6.20</core_client_version>
< |
|
|
|
|
|
I am running Boinc 6.6.17 on my i7 920 with vista 64 bit o/s.
1xnvidia 9600gt video
I have done the math and have the 64bit apps in the correct folder.
I have made the adjustment to the app_info file,but when I run Boinc Manager
I get parse error in app_info.xml;check xml syntax.
Could someone be so kind as to take a look and give me guidence.
Here is my app_info.xml file.
<app_info>
<app>
<name>astropulse</name>
</app>
<file_info>
<name>ap_5.00r103_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse</app_name>
<version_num>500</version_num>
<flops>5699624678</flops>
<file_ref>
<file_name>ap_5.00r103_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<flops>6586232961</flops>
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8_win_SSSE3x.exe</name>
<executable/>
</file_info>
<file_info>
<name>setiathome_6.08_windows_intelx86__cuda.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx64</platform>
<flops>4433041416</flops>
<file_ref>
<file_name>AK_v8_win_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_intelx64</platform>
<avg_ncpus>0.127970</avg_ncpus>
<max_ncpus>0.127970</max_ncpus>
<flops>7400000000</flops>
<plan_class>cuda</plan_class>
<file_ref>
<file_name>setiathome_6.08_windows_intelx86__cuda.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>
</app_info>
Thanks in advance
____________
  |
|
|
|
|
I get parse error in app_info.xml;check xml syntax.
Could someone be so kind as to take a look and give me guidence.
The first thing that jumps out at me is that the platform entry should be:
<platform>windows_x86_64</platform>
____________
|
|
|
|
|
|
The 64bit AK_V8 filename is 'AK_v8_win_x64_SSSE3x.exe'
while the app_info has the 32bit 'AK_v8_win_SSSE3x.exe' in it.
Claggy |
|
|
|
|
|
Just edited those entries but have state file error missing application file
AK v8__win_64_SSE41.exe,however the app is in the folder.
I now have 8xastropulse wu up and running so something works lol
I will run the out and try again
____________
|
|
|
|
|
Just edited those entries but have state file error missing application file
AK v8__win_64_SSE41.exe,however the app is in the folder.
I now have 8xastropulse wu up and running so something works lol
I will run the out and try again
I assume the misplaced underscores are a typo? It should be AK_v8_win_x64_SSE41.exe . Check the Processes tab in Task Manager to see what is actually running the AP WUs.
____________
|
|
|
|
|
|
ap_5.03r112_sse3.exe*32 are running the ap's
The underscores are correct in the info file.
when I start the manager the cuda.exe
the cudart.dll andcufft.dll's are deleted and I later get the error that there
is no url to download from?
The eta of the 8 ap wu's is 24hrs 2% in 26 mins realtime.
the state file says there is no AK_v8_win_64_sse41.exe and it was correct,
so I coppied a new AK_v8_win_64_sse41.exe to the sei folder and for some reason it got deleted again?
____________
|
|
|
|
|
ap_5.03r112_sse3.exe*32 are running the ap's
The underscores are correct in the info file.
when I start the manager the cuda.exe
the cudart.dll andcufft.dll's are deleted and I later get the error that there
is no url to download from?
The eta of the 8 ap wu's is 24hrs 2% in 26 mins realtime.
So the APs are good. Did you download an optimized CUDA app and DLLs? It sounds like you've mixed the stock app with optimized DLLs or vice versa in some combination. That will cause BM to delete all of the files due to a checksum mismatch.
____________
|
|
|
|
|
|
I downloaded the 64 bit files and coppied them to the seti folder as decribed in the txt in the zip
____________
|
|
|
|
|
|
make sure boinc and the boinc manager are restarted to have the replacement take hold
____________
come fly with us at TSWB. Turn off ASTROPULSE HERE
|
|
|
|
|
I downloaded the 64 bit files and coppied them to the seti folder as decribed in the txt in the zip
What package did you download? There are a lot of them floating around. What was contained in the zip archive?
____________
|
|
|
|
|
|
I exited BM and checked in processes.
I replaced the files and restarted BM here are the start messages.
08/04/2009 22:56:48 Starting BOINC client version 6.6.17 for windows_x86_64
08/04/2009 22:56:48 log flags: task, file_xfer, sched_ops
08/04/2009 22:56:48 Libraries: libcurl/7.19.4 OpenSSL/0.9.8j zlib/1.2.3
08/04/2009 22:56:48 Data directory: C:\ProgramData\BOINC
08/04/2009 22:56:48 Running under account FiveHamlet
08/04/2009 22:56:48 SETI@home Found app_info.xml; using anonymous platform
08/04/2009 22:56:48 SETI@home [error] State file error: missing application file AK_v8_win_64_SSE41.exe
08/04/2009 22:56:48 Processor: 8 GenuineIntel Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz [Intel64 Family 6 Model 26 Stepping 4]
08/04/2009 22:56:48 Processor features: fpu tsc pae nx sse sse2 pni mmx
08/04/2009 22:56:48 OS: Microsoft Windows Vista: Ultimate x64 Editon, Service Pack 1, (06.00.6001.00)
08/04/2009 22:56:48 Memory: 6.00 GB physical, 12.10 GB virtual
08/04/2009 22:56:48 Disk: 224.61 GB total, 163.62 GB free
08/04/2009 22:56:48 Local time is UTC +1 hours
08/04/2009 22:56:48 CUDA device: GeForce 9600 GT (driver version 18208, CUDA version 1.1, 512MB, est. 37GFLOPS)
08/04/2009 22:56:48 [error] Deleting file setiathome_6.08_windows_intelx86__cuda.exe while in use
08/04/2009 22:56:48 [error] Deleting file cudart.dll while in use
08/04/2009 22:56:48 [error] Deleting file cufft.dll while in use
08/04/2009 22:56:48 [error] Deleting file libfftw3f-3-1-1a_upx.dll while in use
08/04/2009 22:56:48 Not using a proxy
08/04/2009 22:56:48 SETI@home URL: http://setiathome.berkeley.edu/; Computer ID: 4859727; location: (none); project prefs: default
08/04/2009 22:56:48 SETI@home General prefs: from SETI@home (last modified 29-Mar-2009 03:20:35)
08/04/2009 22:56:48 SETI@home Host location: none
08/04/2009 22:56:48 SETI@home General prefs: using your defaults
08/04/2009 22:56:48 Preferences limit memory usage when active to 4605.43MB
08/04/2009 22:56:48 Preferences limit memory usage when idle to 5526.52MB
08/04/2009 22:56:48 Preferences limit disk usage to 100.00GB
08/04/2009 22:56:48 file projects/setiathome.berkeley.edu/setiathome_6.08_windows_intelx86__cuda.exe not found
08/04/2009 22:56:48 file projects/setiathome.berkeley.edu/cudart.dll not found
08/04/2009 22:56:48 file projects/setiathome.berkeley.edu/cufft.dll not found
08/04/2009 22:56:48 file projects/setiathome.berkeley.edu/libfftw3f-3-1-1a_upx.dll not found
08/04/2009 22:56:48 [error] No URL for file transfer of setiathome_6.08_windows_intelx86__cuda.exe
08/04/2009 22:56:48 [error] No URL for file transfer of cudart.dll
08/04/2009 22:56:48 [error] No URL for file transfer of cufft.dll
08/04/2009 22:56:48 [error] No URL for file transfer of libfftw3f-3-1-1a_upx.dll
08/04/2009 22:56:48 SETI@home Restarting task ap_25fe09aa_B4_P0_00039_20090408_11812.wu_1 using astropulse_v5 version 503
08/04/2009 22:56:48 SETI@home Restarting task ap_25fe09aa_B3_P1_00061_20090408_29928.wu_0 using astropulse_v5 version 503
08/04/2009 22:56:48 SETI@home Restarting task ap_25fe09aa_B2_P1_00329_20090408_02911.wu_0 using astropulse_v5 version 503
08/04/2009 22:56:48 SETI@home Restarting task ap_25fe09aa_B3_P0_00314_20090408_03326.wu_0 using astropulse_v5 version 503
08/04/2009 22:56:48 SETI@home Restarting task ap_19ja09ac_B2_P1_00174_20090309_31229.wu_2 using astropulse_v5 version 503
08/04/2009 22:56:48 SETI@home Restarting task ap_25fe09aa_B3_P1_00060_20090408_29928.wu_1 using astropulse_v5 version 503
08/04/2009 22:56:48 SETI@home Restarting task ap_25fe09aa_B3_P0_00316_20090408_03326.wu_0 using astropulse_v5 version 503
08/04/2009 22:56:48 SETI@home Restarting task ap_25fe09aa_B4_P0_00038_20090408_11812.wu_1 using astropulse_v5 version 503
08/04/2009 22:56:50 SETI@home Backing off 1 min 0 sec on download of setiathome_6.08_windows_intelx86__cuda.exe
08/04/2009 22:56:50 SETI@home Backing off 1 min 0 sec on download of cudart.dll
08/04/2009 22:56:50 SETI@home Backing off 1 min 0 sec on download of cufft.dll
08/04/2009 22:56:50 SETI@home Backing off 1 min 0 sec on download of libfftw3f-3-1-1a_upx.dll
____________
|
|
|
|
|
|
Remember, don't overwrite your special app_info with the new one from your downloaded package,
If you did, it probably won't have entries for the .dll's and cuda app, so Boinc will delete them.
Just need to amend the file names in the app_info of any AK_V8 apps that you have downloaded,
a little hint to make sure the the app name & app_info entries line up:
on the new app file, click rename, copy the whole filename, then paste it into the app_info where required,
this minimises the risk of typo's.
Claggy |
|
|
|
|
|
I replaced the old app info that is the problem then,so
I will have to edit the downloaded app info into the stock app info?
If I close BM can i reinstall the stock app and then edit the info file
without loosing the AP WU's?
So far the 8xAPulse WU's 4.5% in 1Hr
Just checked in the downloaded app_info file and there is reference to cudart cufft and the cuda exe?
____________
|
|
|
|
|
I replaced the old app info that is the problem then,so
I will have to edit the downloaded app info into the stock app info?
If I close BM can i reinstall the stock app and then edit the info file
without loosing the AP WU's?
So far the 8xAPulse WU's 4.5% in 1Hr
Just checked in the downloaded app_info file and there is reference to cudart cufft and the cuda exe?
Make yourself a Temp folder, Download and copy the following files into it:
ap_5.00r103_SSE3.exe
ap_5.03r112_SSE3.exe
Your Choice of AK_V8 app, the SSSE3 version is Probably Best for Quads or Better,
setiathome_6.08_windows_intelx86__cuda.exe
cudart.dll
cufft.dll
libfftw3f-3-1-1a_upx.dll
Discard any downloaded app_info's, use eithier the one in the opening post in this thread with your flops figures, or the one you posted earlier in this thread,
amend (with Notepad) the AK_V8 entries so they read the same as the actual file names,
Double Check that the apps filenames and the app_info entries agree, Copy files to your setiathome folder including your special app_info.xml
Shut down Boinc 6.6.20, copy all the files (Don't move them, you might need to try again),
Start up Boinc, cancel any remaining downloads for apps/.dlls, Boinc should see that you have them now,
If not shut down Boinc and copy them across again,
The Astropulse WU's that you've started should be no problem.
Claggy |
|
|
|
|
|
This would be a well app_info.xml for only CUDA ?
Message 882987
Thanks!
____________
 
U aren't, or U aren't happy in Ur team? seti.international ! :-)
|
|
|
|
|
|
Thank's Claggy for the detail when I get back from work I will apply as you say.
Just looked at the i7 doing the 8 AP's and they are 42% in 9 hrs so they should be finished by the time I get home.
At that rate that would be approx 10k rac when out of the pending pool.running the Cuda along side whould help S&H no end.
12 Hr shift now.
Thanks
____________
|
|
|
|
|
This would be a well app_info.xml for only CUDA ?
Message 882987
Thanks!
See my Post. |
|
|
|
|
|
@ Claggy
Thanks for reply!
@ all
I don't know why I'm the only one which see 1/2 CUDA performance with > BOINC V6.6.11 .
But.. hmm..
I use now all stock.. BOINC and apps..
I see in BOINC V6.6.20 that the MB CPU apps have 'low' priority.
The CUDA apps have 'lower as normal' priority.
For example - boinc.exe have 'normal' priority.
[TaskManager]
If I use an app_info.xml with opt. MB AK V8.0 app [CPU] and stock MB CUDA app [GPU], I would see the same priorities?
BTW.
..'bad' VLARs with stock CUDA app.. ~ 7 times slower as 'normal' ARs.. huhh.. buhh.. :-(
[~ 8 min. vs. ~ 55 min.]
____________
U aren't, or U aren't happy in Ur team? seti.international ! :-)
|
|
|
|
|
|
Great info. Thanks to all that helped. I managed to get everything up and working with only 1 or 2 errors on different machines. Fixed them right away and everything is ok now. I will leave NNT set until my que is down to nothing and then let them fill back up to see what I get.
Not a single lost WU. Backing up that Boinc directory is critical!
Bravo.
____________
Boinc Wiki
"Great spirits have always encountered violent opposition from mediocre minds." -Albert Einstein |
|
|
|
|
|
bump , good thread! |
|
|
|
|
|
After a LOT of reading and trial and error, I think I've got a good version of the app_info file. I ran a trial of it last night, and it only would run one CUDA, whereas I have two GPU's. I've found the answer to that in the co-processor explanation, and have reverted that back to one instead of two.
But I'm still a bit puzzled by this section:
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.127970</avg_ncpus>
<max_ncpus>0.127970</max_ncpus>
<flops>12000000000</flops>
<plan_class>cuda</plan_class>
<file_ref>
What is the basis for the value in <avg_ncpus> and <max_ncpus>? For the record, I'm running a dual core processor, and the previously mentioned two GPU's.
Finally, my trial run last night resulted in BOINC 6.6.20 downloading almost 800 WU's. most of which were MB 608's. I'm sure my calcs for the various classes based on fpops are correct, and BOINC approximated my GPU's at 65Gflops, so I used 13000000000 flops in 608. But I clearly missed something, as the amount of work downloaded is way beyond the 2 day cache I try to maintain. Help!!?? |
|
|
|
|
After a LOT of reading and trial and error, I think I've got a good version of the app_info file. I ran a trial of it last night, and it only would run one CUDA, whereas I have two GPU's. I've found the answer to that in the co-processor explanation, and have reverted that back to one instead of two.
But I'm still a bit puzzled by this section:
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.127970</avg_ncpus>
<max_ncpus>0.127970</max_ncpus>
<flops>12000000000</flops>
<plan_class>cuda</plan_class>
<file_ref>
What is the basis for the value in <avg_ncpus> and <max_ncpus>? For the record, I'm running a dual core processor, and the previously mentioned two GPU's.
Finally, my trial run last night resulted in BOINC 6.6.20 downloading almost 800 WU's. most of which were MB 608's. I'm sure my calcs for the various classes based on fpops are correct, and BOINC approximated my GPU's at 65Gflops, so I used 13000000000 flops in 608. But I clearly missed something, as the amount of work downloaded is way beyond the 2 day cache I try to maintain. Help!!??
The <avg_ncpus> tells boinc how much of a cpu it will use on average. The <max_ncpus> tells it the maximum cpu it will use.
As you can see approx .13 (or 13%) of a cpu is required, the rest is available for boinc to run a cpu task with.
At the beginning of the boinc log (look under the messages tab) it will display details about your gpus. If it found 2 then it will say what they are. Assuming that it finds 2 then it should run 2 cpu wu at the same time as 2 cuda wu.
____________
BOINC blog
|
|
|
|
|
|
Hi,
Does 6.6.20 handle MB-only on CPU and CUDA? There are quite a few combos arund, and one of my computers has ample GPU power but not quite up to par when it comes to CPU (AP). I therefore only want the CPUs and GPU to process S@H MB.
My test so far only downloads 603 app and thus the GPU is idle. Boinc Manager does not log any errors or missing files, so it appears this is out of app_info control...?
Excerpt from log:
18.04.2009 14:17:26 Starting BOINC client version 6.6.20 for windows_intelx86
18.04.2009 14:17:26 log flags: task, file_xfer, sched_ops
18.04.2009 14:17:26 Libraries: libcurl/7.19.4 OpenSSL/0.9.8j zlib/1.2.3
18.04.2009 14:17:26 Data directory: C:\ProgramData\BOINC
18.04.2009 14:17:26 Running under account exchTestBruker
18.04.2009 14:17:26 SETI@home Found app_info.xml; using anonymous platform
18.04.2009 14:17:26 Processor: 8 GenuineIntel Intel(R) Xeon(R) CPU E5320 @ 1.86GHz [x86 Family 6 Model 15 Stepping 7]
18.04.2009 14:17:26 Processor features: fpu tsc pae nx sse sse2 pni mmx
18.04.2009 14:17:26 OS: Microsoft Windows 7: x86 Editon, (06.01.7000.00)
18.04.2009 14:17:26 Memory: 3.00 GB physical, 6.29 GB virtual
18.04.2009 14:17:26 Disk: 135.89 GB total, 13.96 GB free
18.04.2009 14:17:26 Local time is UTC +2 hours
18.04.2009 14:17:26 CUDA device: GeForce GTX 285 (driver version 18171, CUDA version 1.3, 1024MB, est. 127GFLOPS)
18.04.2009 14:17:26 Not using a proxy
18.04.2009 14:17:26 SETI@home URL: http://setiathome.berkeley.edu/; Computer ID: 3447503; location: home; project prefs: default
18.04.2009 14:17:26 SETI@home General prefs: from SETI@home (last modified 10-Apr-2009 19:59:40)
18.04.2009 14:17:26 SETI@home Computer location: home
18.04.2009 14:17:26 General prefs: using separate prefs for home
18.04.2009 14:17:26 Reading preferences override file
18.04.2009 14:17:26 Preferences limit memory usage when active to 1534.37MB
18.04.2009 14:17:26 Preferences limit memory usage when idle to 2761.86MB
18.04.2009 14:17:26 Preferences limit disk usage to 14.03GB
18.04.2009 14:17:26 SETI@home Restarting task 09fe09ac.29909.214879.14.8.139_1 using setiathome_enhanced version 603
Morten
____________
|
|
|
|
|
Hi,
Does 6.6.20 handle MB-only on CPU and CUDA? There are quite a few combos arund, and one of my computers has ample GPU power but not quite up to par when it comes to CPU (AP). I therefore only want the CPUs and GPU to process S@H MB.
My test so far only downloads 603 app and thus the GPU is idle. Boinc Manager does not log any errors or missing files, so it appears this is out of app_info control...?
Excerpt from log:
18.04.2009 14:17:26 Starting BOINC client version 6.6.20 for windows_intelx86
18.04.2009 14:17:26 log flags: task, file_xfer, sched_ops
18.04.2009 14:17:26 Libraries: libcurl/7.19.4 OpenSSL/0.9.8j zlib/1.2.3
18.04.2009 14:17:26 Data directory: C:\ProgramData\BOINC
18.04.2009 14:17:26 Running under account exchTestBruker
18.04.2009 14:17:26 SETI@home Found app_info.xml; using anonymous platform
18.04.2009 14:17:26 Processor: 8 GenuineIntel Intel(R) Xeon(R) CPU E5320 @ 1.86GHz [x86 Family 6 Model 15 Stepping 7]
18.04.2009 14:17:26 Processor features: fpu tsc pae nx sse sse2 pni mmx
18.04.2009 14:17:26 OS: Microsoft Windows 7: x86 Editon, (06.01.7000.00)
18.04.2009 14:17:26 Memory: 3.00 GB physical, 6.29 GB virtual
18.04.2009 14:17:26 Disk: 135.89 GB total, 13.96 GB free
18.04.2009 14:17:26 Local time is UTC +2 hours
18.04.2009 14:17:26 CUDA device: GeForce GTX 285 (driver version 18171, CUDA version 1.3, 1024MB, est. 127GFLOPS)
18.04.2009 14:17:26 Not using a proxy
18.04.2009 14:17:26 SETI@home URL: http://setiathome.berkeley.edu/; Computer ID: 3447503; location: home; project prefs: default
18.04.2009 14:17:26 SETI@home General prefs: from SETI@home (last modified 10-Apr-2009 19:59:40)
18.04.2009 14:17:26 SETI@home Computer location: home
18.04.2009 14:17:26 General prefs: using separate prefs for home
18.04.2009 14:17:26 Reading preferences override file
18.04.2009 14:17:26 Preferences limit memory usage when active to 1534.37MB
18.04.2009 14:17:26 Preferences limit memory usage when idle to 2761.86MB
18.04.2009 14:17:26 Preferences limit disk usage to 14.03GB
18.04.2009 14:17:26 SETI@home Restarting task 09fe09ac.29909.214879.14.8.139_1 using setiathome_enhanced version 603
Morten
You could try the following, but no warranty expressed or implied...
Its a copy of the original app_info minus the astropulse bits. I've even calculated the flops figure for your GTX285, but you'll need to do the cpu flops numbers as I don't have access to your <f_pops> figure. See the 1st message in this thread for instructions on how to calculate this number.
<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8_win_SSSE3x.exe</name>
<executable/>
</file_info>
<file_info>
<name>setiathome_6.08_windows_intelx86__cuda.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx86</platform>
<flops>4127010920</flops>
<file_ref>
<file_name>AK_v8_win_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.127970</avg_ncpus>
<max_ncpus>0.127970</max_ncpus>
<flops>25400000000</flops>
<plan_class>cuda</plan_class>
<file_ref>
<file_name>setiathome_6.08_windows_intelx86__cuda.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>
</app_info>
____________
BOINC blog
|
|
|
|
|
Hi,
Does 6.6.20 handle MB-only on CPU and CUDA? There are quite a few combos arund, and one of my computers has ample GPU power but not quite up to par when it comes to CPU (AP). I therefore only want the CPUs and GPU to process S@H MB.
My test so far only downloads 603 app and thus the GPU is idle. Boinc Manager does not log any errors or missing files, so it appears this is out of app_info control...?
I don't see why you feel your CPU isn't up to AP work: my dual E5320 is churning them out quite happily.
But returning to your question: yes, BOINC v6.6.20 can handle MB/CPU v6.03 and MB/CUDA v6.08 at the same time. As others have noted, the SETI scheduler can be a bit reluctant to hand out MB work to CPUs (I think all the CUDA hosts gobble it up first, and the CPUs only get left-overs if they're lucky). Provided you've set up the app_info.xml as in the opening post of this thread (minus the AP bits if you really don't want to run them), then all should be well.
Perhaps check the SETI@home 'Properties' (new command button on the projects tab), to make sure your CUDA work-fetch isn't suffering any sort of back-off. |
|
|
|
|
....but you'll need to do the cpu flops numbers as I don't have access to your <f_pops> figure.
<p_fpops> (sic) for a Core2 is often very close to the speed in GHz. My E5320 is showing <p_fpops> = 1828798802.551730 - and with a Xeon, there won't be any overclocking to worry about. |
|
|
|
|
....but you'll need to do the cpu flops numbers as I don't have access to your <f_pops> figure.
<p_fpops> (sic) for a Core2 is often very close to the speed in GHz. My E5320 is showing <p_fpops> = 1828798802.551730 - and with a Xeon, there won't be any overclocking to worry about.
I keep getting that one wrong.
@ Morten, use the <p_fpops> number to calculate the <flops> value.
I just got myself a pair of GTS250's so have one more cuda-capable machine. I swapped out a 9800GT from one and put the other one in a machine that didn't have any. I like them so much I ordered another pair :-)
____________
BOINC blog
|
|
|
|
|
|
Hi,
All is ok - it just took many downloads batches before 608 was downloaded. Why I don't know.
Thanks for your feedback.
Morten
____________
|
|
|
|
|
I don't see why you feel your CPU isn't up to AP work: my dual E5320 is churning them out quite happily.
Hi
This is a Dell computer and it cannot be overclocked unless I take my chances with replacing the BIOS, so the chrunch-time IMO is just too slow.
Morten
____________
|
|
|
|
|
|
I have a Dell 2950 with two 5320s running Astropulse at stock speed. It has an RAC >10,000 and 1.8 million total credit.
____________
|
|
|
|
|
|
I seem to have done something somewhere as processing times on my work units have increased dramatically.
Here are the specs and my app_info file, I am using optimized clients
Found app_info.xml; using anonymous platform
Processor: 2 GenuineIntel Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz [x86 Family 6 Model 15 Stepping 6]
Processor features: fpu tsc pae nx sse sse2 mmx
CUDA device: GeForce 8500 GT (driver version 18250, CUDA version 1.1, 1024MB, est. 5GFLOPS)
<app_info>
<app>
<name>astropulse</name>
</app>
<file_info>
<name>ap_5.00r103_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse</app_name>
<version_num>500</version_num>
<flops>4643141391</flops>
<file_ref>
<file_name>ap_5.00r103_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<flops>4663777574.96</flops>
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>MB_6.08_mod_CUDA_V11_VLARKill_refined.exe</name>
<executable/>
</file_info>
<file_info>
<name>MB_6.08_mod_CUDA_V11_VLARKill_refined.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx86</platform>
<flops>3611332193</flops>
<file_ref>
<file_name>MB_6.08_mod_CUDA_V11_VLARKill_refined.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.127970</avg_ncpus>
<max_ncpus>0.127970</max_ncpus>
<flops>10000000000</flops>
<plan_class>cuda</plan_class>
<file_ref>
<file_name>MB_6.08_mod_CUDA_V11_VLARKill_refined.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>
</app_info>
Any help would be appreciated. If there is an error somewhere in my app_info can someone point it out please.
Cuda tasks seem to take 2hrs (0.13 cpus, I cuda)
AP seems to be 35-40 hours.
____________
 |
|
|
|
|
|
Your app_info has 'MB_6.08_mod_CUDA_V11_VLARKill_refined.exe' referenced too often,
With that app_info you will be trying to run 3 Cuda WU's at once, and none on the CPU,
you need to change the 603 entry to an AK_V8 CPU app, and one of the
<file_info>
<name>MB_6.08_mod_CUDA_V11_VLARKill_refined.exe</name>
<executable/>
to the same CPU app.
Claggy |
|
|
|
|
|
Had a feeling it might have been that but wasn't 100% sure.
Thank you for the response.
____________
|
|
|
|
|
I have a Dell 2950 with two 5320s running Astropulse at stock speed. It has an RAC >10,000 and 1.8 million total credit.
Mine has a rac of ~6000 and that's with CPU+GPU and you're rac'ing 10k on stock CPU speed without GPU - that's really odd! A high percentage of AP crunching cannot explain the rac difference...
I haven't tried with current AP, so based on your input I'll do a test run for some weeks to see how the rac changes.
Morten
____________
|
|
|
|
|
|
So this will be correct then now?
<app_info>
<app>
<name>astropulse</name>
</app>
<file_info>
<name>ap_5.00r103_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse</app_name>
<version_num>500</version_num>
<flops>4643141391</flops>
<file_ref>
<file_name>ap_5.00r103_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<flops>4663777574.96</flops>
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>MB_6.08_mod_CUDA_V11_VLARKill_refined.exe</name>
<executable/>
</file_info>
<file_info>
<name>AK_v8_win_SSE3.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx86</platform>
<flops>3611332193</flops>
<file_ref>
<file_name>AK_v8_win_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.127970</avg_ncpus>
<max_ncpus>0.127970</max_ncpus>
<flops>10000000000</flops>
<plan_class>cuda</plan_class>
<file_ref>
<file_name>MB_6.08_mod_CUDA_V11_VLARKill_refined.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>
</app_info>
____________
|
|
|
|
|
I don't see why you feel your CPU isn't up to AP work: my dual E5320 is churning them out quite happily.
Hi
This is a Dell computer and it cannot be overclocked unless I take my chances with replacing the BIOS, so the chrunch-time IMO is just too slow.
Morten
Mine is also a Dell (Precision 490): I don't think even a BIOS replacement would allow overclocking! The speed of these Xeons is controlled by voltages applied to pins in the CPU holder: overclocking involves covering them with little bits of insulating tape....
But I don't mind running AP on it: they're positively racy compared with the 4-month CPDN tasks I'm running on three of the cores. |
|
|
|
|
I have a Dell 2950 with two 5320s running Astropulse at stock speed. It has an RAC >10,000 and 1.8 million total credit.
Mine has a rac of ~6000 and that's with CPU+GPU and you're rac'ing 10k on stock CPU speed without GPU - that's really odd!
Are you running optimized apps?
____________
|
|
|
|
|
|
That looks Better, But replace the AK_V8_SSE3 app with the SSSE3 app,
use CPU-Z to confirm your C2D supports SSSE3 first,
Claggy |
|
|
|
|
I have a Dell 2950 with two 5320s running Astropulse at stock speed. It has an RAC >10,000 and 1.8 million total credit.
Mine has a rac of ~6000 and that's with CPU+GPU and you're rac'ing 10k on stock CPU speed without GPU - that's really odd!
Are you running optimized apps?
I sure do - Raistmers v10a, but now I've downloaded lot's of APs in order to see if that'll up the rac (+4000 that is...).
Morten
____________
|
|
|
|
|
I've downloaded lot's of APs in order to see if that'll up the rac (+4000 that is...).
Be very patient.
____________
|
|
|
|
|
|
To FLOPS or not to FLOPS ?
I've got two questions in regards to the flops-entry:
1: Will a future BOINC version control this calculation?
2: What is the consequence of dropping the flops entry in app_info?
When you have many computers this current implementation is very time comsuming and it's also very easy to miscalculate.
Morten
____________
|
|
|
|
|
What is the consequence of dropping the flops entry in app_info?
Very little to none. Your initial estimates for time required for tasks will be off, but BOINC figures them out soon enough. They're not very accurate anyway. I quit entering values for flops and platform in app_info.xml quickly. With a mix of machines running 32 and 64 bit operating systems with varying CUDA capability, I found it to be WAY more trouble than it's worth.
____________
|
|
|
|
|
|
You mean I did all that math for nothing??? :D
____________
PROUD MEMBER OF Team Starfire World BOINC |
|
|
|
|
What is the consequence of dropping the flops entry in app_info?
Very little to none. Your initial estimates for time required for tasks will be off, but BOINC figures them out soon enough. They're not very accurate anyway. I quit entering values for flops and platform in app_info.xml quickly. With a mix of machines running 32 and 64 bit operating systems with varying CUDA capability, I found it to be WAY more trouble than it's worth.
That's what I thought too, and ditto - I deleted the entries as well.
But it seems BOINC downloads way too many WUs for the report deadline, so I don't think it's working the way I'd like.
I will monitor this and furter lower my value for the work cache.
Morten
____________
|
|
|
|
|
What is the consequence of dropping the flops entry in app_info?
Very little to none. Your initial estimates for time required for tasks will be off, but BOINC figures them out soon enough. They're not very accurate anyway. I quit entering values for flops and platform in app_info.xml quickly. With a mix of machines running 32 and 64 bit operating systems with varying CUDA capability, I found it to be WAY more trouble than it's worth.
That's what I thought too, and ditto - I deleted the entries as well.
But it seems BOINC downloads way too many WUs for the report deadline, so I don't think it's working the way I'd like.
I will monitor this and furter lower my value for the work cache.
I am running with zero "connect about every" and three "additional work buffer" using 6.6.20 on various versions of Windows and Linux. It seems quite accurate relative to the problems 6.4.x had.
____________
|
|
|
|
|
What is the consequence of dropping the flops entry in app_info?
Very little to none. Your initial estimates for time required for tasks will be off, but BOINC figures them out soon enough. They're not very accurate anyway. I quit entering values for flops and platform in app_info.xml quickly. With a mix of machines running 32 and 64 bit operating systems with varying CUDA capability, I found it to be WAY more trouble than it's worth.
That's what I thought too, and ditto - I deleted the entries as well.
But it seems BOINC downloads way too many WUs for the report deadline, so I don't think it's working the way I'd like.
I will monitor this and furter lower my value for the work cache.
Morten
It really doesn't matter what absolute value you put in. What makes a difference are the relative speeds of the different applications on your particular hardware - both CPU and GPU.
The quote from Andy above says 'BOINC figures them out'. Not quite true: BOINC will try to figure them out, but will keep getting four different answers (AP, AP_v5, MB/CPU, and MB/CUDA). In particular, if you don't put in the CUDA speed, BOINC will assume that it runs at the same speed as your CPU. Not if it's a decent CUDA card, it won't be. So a run of CUDA task completions will drive BOINC's estimate downwards: in its naivety, BOINC will assume that AP is as optimised as your CUDA card, and will over-fetch. Then an AP task will finish, BOINC will switch to a different estimate - and won't fetch any more work for possibly days. For anything.
The object of the calculations is to avoid these wild lurches in Duration Correction Factor. They don't have to be exact, but the easiest way to get the decimal point in the right place is to paste <p_fpops> into Windows Calculator and paste the result back. It really doesn't take long, and you only have to do it once per machine - once per class of machine, if you have at least some which are broadly similar. Believe me, a little bit of effort here keeps the work flowing smoothly and efficiently for a long time to come - my productivity has greatly increased since I first posted a version of this procedure at Beta six weeks ago.
There are moves afoot to include separate DCF calculations for the separate applications in a future version of BOINC - at which point you can all put calc.exe away again - but that won't be until at least BOINC v6.8, and so far as I know they haven't even started work on that yet. |
|
|
|
|
|
Thanks for the clarification Richard.
When Mark posted his app_info.xml file I too wondered what all that was about. I went through all the calcs and have created separate directories on the server for each machine in my inventory. Looks like the only change I will have to make will be with the graphics card calcs as they will likely be the only thing changing for a while.
G
____________
Boinc Wiki
"Great spirits have always encountered violent opposition from mediocre minds." -Albert Einstein |
|
|
|
|
|
Ok, I have an 8500gt that is estimated at 5 GFLOPS. When I report 6.08s it drags the time to completion of the APs down. So, I should raise the GFLOP in my app_info for the GPU ? Maybe refigure for 6GFLOPs instead of 5?
By the time I've finished an AP V5 I've turned in so many 6.08s the Time to completion guesstimate on the rest of the APs are down to around 12 hours. It really takes me about 60 hours each. Also, when the APs do report it jumps the time for the 6.08s up to around 20 hours and the APs to upwards of 100 hours. I'm sure I did the math right but this is really confusing.
____________
PROUD MEMBER OF Team Starfire World BOINC |
|
|
|
|
Ok, I have an 8500gt that is estimated at 5 GFLOPS. When I report 6.08s it drags the time to completion of the APs down. So, I should raise the GFLOP in my app_info for the GPU ? Maybe refigure for 6GFLOPs instead of 5?
By the time I've finished an AP V5 I've turned in so many 6.08s the Time to completion guesstimate on the rest of the APs are down to around 12 hours. It really takes me about 60 hours each. Also, when the APs do report it jumps the time for the 6.08s up to around 20 hours and the APs to upwards of 100 hours. I'm sure I did the math right but this is really confusing.
This is what I don't understand in the real world. As Richard posts, DCF should be going all over the place because of CUDA 608s vs CPU AP v5s. As I noted elsewhere, the DCF on some of my CUDA capable machines is as low as 0.02. But BOINC 6.6.20 does not go crazy with downloading APs. Thankfully, but I don't understand why not.
The real fix, as Richard also posts, will be to have separate DCFs for each application.
____________
|
|
|
|
|
|
What final flops figures are you using for AP, AP_v5, MB603 and MB608?
Claggy |
|
|
|
|
|
Why does CPU-Z say I have SSE3 and Boinc says SSE2? Which is the correct I wonder... |
|
|
|
|
Why does CPU-Z say I have SSE3 and Boinc says SSE2? Which is the correct I wonder...
CPU-Z should be Correct, Boinc only reports what the OS reports.
Claggy |
|
|
|
|
|
Sorry, had to wait for one to finish before I stopped SETI.
My PFPOPs 1851545749
Est. GFLOPs 5Gflops
AP 5.00 4194755270
AP 5.03 4847272757
MB 6.03 3269311494
MB 6.08 1000000000
____________
PROUD MEMBER OF Team Starfire World BOINC |
|
|
|
|
|
The figures you posted are correct, double check your app_info figures,
but i assume you got them from there, so it should't be different,
on my E8500, AP_v5 tends to drive completion times down,
while MB608 eithier drives completion times up or down depending on the AR,
and you're running a VLAR killer, so they won't be driving completion times really high,
Must be something to do with the GPU being very slow, compared to MarkJ's,
I'd try lowering the GPU flops figure first, say 800000000
Put this in a cc_config.xml and monitor what dcf is doing first:
<cc_config>
<log_flags>
<dcf_debug>1</dcf_debug>
</log_flags>
</cc_config>
Claggy |
|
|
|
|
|
Ok, a cuda task finished. This is the DCF
4/19/2009 5:47:04 PM SETI@home [dcf] DCF: 0.576175->0.528535, raw_ratio 0.099773, adj_ratio 0.173164
and a 6.03 finished with this dcf
4/19/2009 5:51:17 PM SETI@home [dcf] DCF: 0.528535->0.523195, raw_ratio 0.475133, adj_ratio 0.898962
and another 6.03
4/19/2009 6:04:16 PM SETI@home [dcf] DCF: 0.523195->0.516565, raw_ratio 0.456895, adj_ratio 0.873279
____________
PROUD MEMBER OF Team Starfire World BOINC |
|
|
|
|
|
Well you dcf is getting driven down, should end up around 0.2,
you might find particular AR's drive it and completion times back up a bit,
just monitor it for now, let us know what astropulse does,
Claggy
Edit: your CPU time spent feeding the GPU is 4 times what mine is (9800GTX+ on PCI-X 16), i wonder what difference that makes? |
|
|
|
|
|
It may take awhile before I get to another Astropulse. I got swamped with a bunch of 6.03s while ttc was down. I'd like to clear some of them out before I do another AP. As I said, the Astropulse takes me 60+ hours to complete.
____________
PROUD MEMBER OF Team Starfire World BOINC |
|
|
|
|
....but you'll need to do the cpu flops numbers as I don't have access to your <f_pops> figure.
<p_fpops> (sic) for a Core2 is often very close to the speed in GHz. My E5320 is showing <p_fpops> = 1828798802.551730 - and with a Xeon, there won't be any overclocking to worry about.
And Morten's E5320 Windows 7 host shows "Measured floating point speed 1807.52 million ops/sec" which indicates a <p_fpops> of 1807520000. Six digits of accuracy is more than ample. Joe |
|
|
|
|
|
Im running an app_info very similar to the one featured in this post. I have upgraded to 6.6.20 in the hope of finally being able to stop micro-managing all my hosts, but Im still having problems with CUDA/AP units. Im running a dual core with a 8800GT and ideally would like the CPU to crunch AP only while the GPU crunches MB units. I have set max_cpu to 3 previously, should I be undoing this in 6.6.20. I am running all the latest optimised apps
I keep getting in from work to find myy host crunching 3 AP units on 2 cores with the GPU idle.
What is the best way to resolve this please?
On another seperate note, is there a problem with BOINC stats or the berkley databases as I have had a total of 450 approx units credit from SETI???
http://boincstats.com/stats/boinc_user_graph.php?pr=bo&id=1405036
Thx for the help
____________
|
|
|
|
|
I have set max_cpu to 3 previously, should I be undoing this in 6.6.20.
On another seperate note, is there a problem with BOINC stats or the berkley databases as I have had a total of 450 approx units credit from SETI???
Definitely get rid of the max_cpus setting. BM 6.6.20 has this function built in.
As for the stats, they are pulled from the replica database which has been down several days for repairs.
____________
|
|
|
|
|
I have set max_cpu to 3 previously, should I be undoing this in 6.6.20.
On another seperate note, is there a problem with BOINC stats or the berkley databases as I have had a total of 450 approx units credit from SETI???
Definitely get rid of the max_cpus setting. BM 6.6.20 has this function built in.
As for the stats, they are pulled from the replica database which has been down several days for repairs.
Actually there might be further confusion here. The max_ncpus [sic] setting is in app_info.xml and is typically around 0.1 - this is used for feeding the GPU data. A setting of three sounds more typical for the ncpus [sic] setting in cc_config.xml which is the one that is no longer necessary. Get rid of cc_config.xml entirely unless you are using it for debugging purposes.
____________
|
|
|
|
|
|
Ok..
Cheers for the help, will apply the changes when I get in tonight.
Thanks again
____________
|
|
|
|
|
|
Ok, I have deleted my cc_config file and restarted boinc and Im crunching 2 AP WU, but no CUDA units, my GPU is idle?? What am I missing, strangley I have noticed that I no longer have an app_info file (yet Im still using R112 for the AP units) Is this a result of the move to 6.6.20?
____________
|
|
|
|
|
It may take awhile before I get to another Astropulse. I got swamped with a bunch of 6.03s while ttc was down. I'd like to clear some of them out before I do another AP. As I said, the Astropulse takes me 60+ hours to complete.
Well, I finished one. The time to completion jumped back up for both the APs and the Cuda work. I decided to make a small change in the FLOPS for my Cuda work. I re-figured it for 6GFlops instead of 5 and the TTC is a lot closer to what it should be.
I also suspended the APs that weren't running so that I am only running one AP and one MB on my CPUs. this may have helped it figure out the right DCF. This may change today though, I managed to download a bunch of shorties for my Cuda this morning. :)
____________
PROUD MEMBER OF Team Starfire World BOINC |
|
|
|
|
|
MadMaC,
6.6.20 should not have caused your app_info to disappear. It still needs to be in there somewhere.
____________
PROUD MEMBER OF Team Starfire World BOINC |
|
|
BrodoVolunteer tester
Send message
Joined: Feb 14 04
Posts: 364
Credit: 13,363,825
RAC: 56,105
|
|
If I'm running 2 video cards of different speeds. Which one do I use to calculate the Gflops as per Marks instructions ? The fast one or the slow one ?
Brodo |
|
|
|
|
If I'm running 2 video cards of different speeds. Which one do I use to calculate the Gflops as per Marks instructions ? The fast one or the slow one ?
Brodo
At message 880869, a long way down (or up - depending on you preferred order) this same thread, I suggested that using the speed of your faster card would give the smoothest DCF / cache fill experience.
But since then, I've realised that this will fill your cache as if you had two fast cards. Be a little cautious with the cache setting if you follow that advice. |
|
|
|
|
|
I believe someone also suggested you average the two and figure from that.
____________
PROUD MEMBER OF Team Starfire World BOINC |
|
|
|
|
I believe someone also suggested you average the two and figure from that.
Did they give any reasoning? My approach, by targeting DCF, is designed never to miss a CPU (AP) deadline in the four-way environment described in this thread title - at the expense, as I've just posted, of possibly missing CUDA deadlines if you over-do the cache setting. |
|
|
|
|
|
I can't find the post where I read that now. I think it was just to keep the figure low enough so that BM wouldn't get the idea you had two really fast cards and load you up beyond what you could finish.
____________
PROUD MEMBER OF Team Starfire World BOINC |
|
|
|
|
I can't find the post where I read that now. I think it was just to keep the figure low enough so that BM wouldn't get the idea you had two really fast cards and load you up beyond what you could finish.
Or having it too high, and WU's taking too long on the slow card and getting maximum time exceeded,
But i've only seen that on Astropulse so far.
Claggy |
|
|
|
|
I can't find the post where I read that now. I think it was just to keep the figure low enough so that BM wouldn't get the idea you had two really fast cards and load you up beyond what you could finish.
I remember reading this as well.
Before this thread, I had to read lots of threads to figure out how to set up the app_info properly. I do not remember where I read it either... :(
Regards,
G
____________
Boinc Wiki
"Great spirits have always encountered violent opposition from mediocre minds." -Albert Einstein |
|
|
BrodoVolunteer tester
Send message
Joined: Feb 14 04
Posts: 364
Credit: 13,363,825
RAC: 56,105
|
If I'm running 2 video cards of different speeds. Which one do I use to calculate the Gflops as per Marks instructions ? The fast one or the slow one ?
Brodo
At message 880869, a long way down (or up - depending on you preferred order) this same thread, I suggested that using the speed of your faster card would give the smoothest DCF / cache fill experience.
But since then, I've realised that this will fill your cache as if you had two fast cards. Be a little cautious with the cache setting if you follow that advice.
Thanks Richard - I knew I'd seen the answer somewhere in the dim dark past but couldn't find it again when I needed it.
Am now up and running using the "No AP" version of your app_info file. I only run a 1.5 day cache so time outs are not a problem
Strange, AK_v8 even picked up the 2 units that were half crunched by the stock 6.03 app and carried on with them. I thought it would shred them and start 2 new ones
Brodo
|
|
|
|
|
Strange, AK_v8 even picked up the 2 units that were half crunched by the stock 6.03 app and carried on with them. I thought it would shred them and start 2 new ones
Brodo
No surprise, Lunatics apps are polite and well-mannered like that. :-)
[Well, they are when we get them, and the corresponding app_info, right] |
|
|
|
|
|
I looked in My client_state.xml file and <p_flops> doesn't exist there, I have a GTX295 and I run MB on both the Intel Q9300 Quad Core cpu(3.51GHz) and on the gpus(the GTX295), all this is running under XP x64. Is there anywhere else in Boinc 6.6.20 where It could be located at?
I do have this in client state of course:
</xml_signature>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>1.000000</avg_ncpus>
<max_ncpus>1.000000</max_ncpus>
<flops>3512976066.004993</flops>
<file_ref>
<file_name>AK_v8_win_x64_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.010000</avg_ncpus>
<max_ncpus>0.010000</max_ncpus>
<flops>3512976066.004993</flops>
<plan_class>cuda</plan_class>
<file_ref>
<file_name>MB_6.08_mod_CUDA_V11_VLARKill_refined.exe</file_name>
Edit: I set My flops level at <flops>12000000000</flops> for the time being as a placeholder, It's better than nothing I suspect.
<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8_win_x64_SSSE3x.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>AK_v8_win_x64_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>MB_6.08_mod_CUDA_V11_VLARKill_refined.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<plan_class>cuda</plan_class>
<avg_ncpus>0.010000</avg_ncpus>
<max_ncpus>0.010000</max_ncpus>
<flops>12000000000</flops>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB_6.08_mod_CUDA_V11_VLARKill_refined.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
</app_version>
</app_info>
____________
 My Farm/PCs Specs
 |
|
|
Fred WVolunteer tester
Send message
Joined: Jun 13 99
Posts: 2175
Credit: 5,926,236
RAC: 19,577
|
I looked in My client_state.xml file and <p_flops> doesn't exist there, I have a GTX295 and I run MB on both the Intel Q9300 Quad Core cpu(3.51GHz) and on the gpus(the GTX295). Is there anywhere else in Boinc 6.6.20 where It could be located at?
I do have this in client state of course:
</xml_signature>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>1.000000</avg_ncpus>
<max_ncpus>1.000000</max_ncpus>
<flops>3512976066.004993</flops>
<file_ref>
<file_name>AK_v8_win_x64_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.010000</avg_ncpus>
<max_ncpus>0.010000</max_ncpus>
<flops>3512976066.004993</flops>
<plan_class>cuda</plan_class>
<file_ref>
<file_name>MB_6.08_mod_CUDA_V11_VLARKill_refined.exe</file_name>
I'm running my Q9450 (o/c) + GTX295 with the CUDA flops set to 21200000000 and the AK-V8 flops set to 6351283655.
Works for me.
F.
____________
|
|
|
|
|
|
Look for P_FPOPS
____________
PROUD MEMBER OF Team Starfire World BOINC |
|
|
|
|
Look for P_FPOPS
Ok I found It and It's 3512976066.004993 so now what? multiply It by 0.2?
Edit: Ok I'm trying this out: <flops>00702595213</flops>
____________
My Farm/PCs Specs
|
|
|
|
|
Look for P_FPOPS
Ok I found It and It's 3512976066.004993 so now what? multiply It by 0.2?
NO, that's CPU flops, get GPU flops from your Boinc log on start-up,
It'll be something like 87 (Est.Gflops) times it by 1000000000 then by 0.2
Claggy |
|
|
Fred WVolunteer tester
Send message
Joined: Jun 13 99
Posts: 2175
Credit: 5,926,236
RAC: 19,577
|
Look for P_FPOPS
Ok I found It and It's 3512976066.004993 so now what? multiply It by 0.2?
Edit: Ok I'm trying this out: <flops>00702595213</flops>
You need the P_FPops for CPU: That should be multiplied by 1.75.
Your GPU will be the same as mine - Est 106 GFlops - so you should use 21200000000 for that.
F.
____________
|
|
|
|
|
Look for P_FPOPS
Ok I found It and It's 3512976066.004993 so now what? multiply It by 0.2?
Edit: Ok I'm trying this out: <flops>00702595213</flops>
You need the P_FPops for CPU: That should be multiplied by 1.75.
Your GPU will be the same as mine - Est 106 GFlops - so you should use 21200000000 for that.
F.
Ok now where do I put the flops for the cpu in the app info file?
How's this?
And the flops is the fpops number after being multiplied by 1.75.
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8_win_x64_SSSE3x.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<flops>6147708115</flops>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>AK_v8_win_x64_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
____________
My Farm/PCs Specs
|
|
|
Fred WVolunteer tester
Send message
Joined: Jun 13 99
Posts: 2175
Credit: 5,926,236
RAC: 19,577
|
|
Here's a snip of mine:
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>1.000000</avg_ncpus>
<max_ncpus>1.000000</max_ncpus>
<flops>6351283655</flops>
<file_ref>
<file_name>AK_v8_win_x64_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.150000</avg_ncpus>
<max_ncpus>0.150000</max_ncpus>
<flops>21200000000</flops>
<plan_class>cuda</plan_class>
<file_ref>
<file_name>setiathome_6.08_windows_intelx86__cuda.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>
F.
____________
|
|
|
|
|
Here's a snip of mine:
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>1.000000</avg_ncpus>
<max_ncpus>1.000000</max_ncpus>
<flops>6351283655</flops>
<file_ref>
<file_name>AK_v8_win_x64_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.150000</avg_ncpus>
<max_ncpus>0.150000</max_ncpus>
<flops>21200000000</flops>
<plan_class>cuda</plan_class>
<file_ref>
<file_name>setiathome_6.08_windows_intelx86__cuda.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>
F.
I'm assimilating the parts of Yours that are missing and making It match order wise to Yours.
Oh and Here's mine:
<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8_win_x64_SSSE3x.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>1.000000</avg_ncpus>
<max_ncpus>1.000000</max_ncpus>
<flops>6147708115</flops>
<file_ref>
<file_name>AK_v8_win_x64_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>MB_6.08_mod_CUDA_V11_VLARKill_refined.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<plan_class>cuda</plan_class>
<avg_ncpus>0.010000</avg_ncpus>
<max_ncpus>0.010000</max_ncpus>
<flops>21200000000</flops>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB_6.08_mod_CUDA_V11_VLARKill_refined.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
</app_version>
</app_info>
____________
My Farm/PCs Specs
|
|
|
Fred WVolunteer tester
Send message
Joined: Jun 13 99
Posts: 2175
Credit: 5,926,236
RAC: 19,577
|
I'm assimilating the parts of Yours that are missing and making It match order wise to Yours.
Should be good to go then as long as it is pointing to your file names.
F.
____________
|
|
|
|
|
I'm assimilating the parts of Yours that are missing and making It match order wise to Yours.
Should be good to go then as long as it is pointing to your file names.
F.
Oh It is, I didn't change that as My last post shows.
____________
My Farm/PCs Specs
|
|
|
|
|
|
Just moving this back to the front page.
____________
PROUD MEMBER OF Team Starfire World BOINC |
|
|
|
|
|
Having some problems... Can I get some help?
Followed instructions and got all of the apps and loaded them. I then modified my app_info and loaded that. Checked for errors and got none, so re-started the network and requested new work. I got several CUDA units that started fine and then the problems started. As I got ap V5 503 units they would download and start then immediately complete with an error that I did not have an "output" file?
I have attached a pic of my message log and my app_info file...
Can someone take a look and throw me a bone?
i7 920 @ 3.5Ghz
12Gb Corsair @ 1600mhz
Vista Ultimate 64bit
9800 GX2 in non SLI
<app_info>
<app>
<name>astropulse</name>
</app>
<file_info>
<name>ap_5.00r103_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse</app_name>
<version_num>500</version_num>
<flops>6859929025</flops>
<file_ref>
<file_name>ap_5.00r103_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>AK_v8_win_x64_SSE41.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<flops>7927029095</flops>
<file_ref>
<file_name>AK_v8_win_x64_SSE41.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8_win_x64_SSE41.exe</name>
<executable/>
</file_info>
<file_info>
<name>setiathome_6.08_windows_intelx86__cuda.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx86</platform>
<flops>5335500352</flops>
<file_ref>
<file_name>AK_v8_win_x64_SSE41.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>.01</avg_ncpus>
<max_ncpus>.01</max_ncpus>
<flops>16600000000</flops>
<plan_class>cuda</plan_class>
<file_ref>
<file_name>setiathome_6.08_windows_intelx86__cuda.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>
</app_info>
____________
Bark Loud! Bite Hard!
|
|
|
|
|
|
Try to check if the files have the correct permissions. They should be the same as the folder. |
|
|
|
|
|
What permisssions?
____________
Bark Loud! Bite Hard!
|
|
|
|
|
|
right-click the file, then under the security tab |
|
|
Fred WVolunteer tester
Send message
Joined: Jun 13 99
Posts: 2175
Credit: 5,926,236
RAC: 19,577
|
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<flops>7927029095</flops>
<file_ref>
<file_name>AK_v8_win_x64_SSE41.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
Well the first thing I notice in your app_info.xml file is that you are trying to use the wrong App for Astropulse v5. The AK_V8 will not process Astropulse - you need the ap_5.03r112_SSE3.exe for that.
F.
____________
|
|
|
|
|
Having some problems... Can I get some help?
Followed instructions and got all of the apps and loaded them. I then modified my app_info and loaded that. Checked for errors and got none, so re-started the network and requested new work. I got several CUDA units that started fine and then the problems started. As I got ap V5 503 units they would download and start then immediately complete with an error that I did not have an "output" file?
I have attached a pic of my message log and my app_info file...
Can someone take a look and throw me a bone?
i7 920 @ 3.5Ghz
12Gb Corsair @ 1600mhz
Vista Ultimate 64bit
9800 GX2 in non SLI
There is a line after the preferences limits
file projects\setiathome.berkeley.edu\ap_5.00r103_SSE3.exe not found
check that
<app_info>
<app>
<name>astropulse</name>
</app>
<file_info>
<name>ap_5.00r103_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse</app_name>
<version_num>500</version_num>
<flops>6859929025</flops>
<file_ref>
<file_name>ap_5.00r103_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>AK_v8_win_x64_SSE41.exe</name> <----- This exe is setiathome_enhanced opt. app, you need this -> ap_5.03r103_SSE3.exe, wrong app can't work.
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<flops>7927029095</flops>
<file_ref>
<file_name>AK_v8_win_x64_SSE41.exe</file_name> <-- here too
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8_win_x64_SSE41.exe</name>
<executable/>
</file_info>
<file_info>
<name>setiathome_6.08_windows_intelx86__cuda.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx86</platform>
<flops>5335500352</flops>
<file_ref>
<file_name>AK_v8_win_x64_SSE41.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>.01</avg_ncpus>
<max_ncpus>.01</max_ncpus>
<flops>16600000000</flops>
<plan_class>cuda</plan_class>
<file_ref>
<file_name>setiathome_6.08_windows_intelx86__cuda.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>
</app_info>
____________
 |
|
|
|
|
|
Yup I added the AK to the AP, My bonehead move...
Changed it to the correct AP 503 and all is well, now I can see what I can do with this new i7!
Thanks again...
____________
Bark Loud! Bite Hard!
|
|
|
|
|
Having some problems... Can I get some help?
Followed instructions and got all of the apps and loaded them. I then modified my app_info and loaded that. Checked for errors and got none, so re-started the network and requested new work. I got several CUDA units that started fine and then the problems started. As I got ap V5 503 units they would download and start then immediately complete with an error that I did not have an "output" file?
...
FWIW, 4 of those AP WUs had a data problem not your fault at all. Specifically, your tasks 1216982434, 1216982874, 1216983056, and 1216984097 quit without producing an output file with:
Error in ap_remove_radar.cpp: generate_envelope: num_ffts_performed < 100. Blanking too much RFI?
They were all from the the B3_P1 channel of 'tapes' from ap_13mr09 or ap_20mr09, which matches what others are seeing. See some recent posts in the Astropulse Errors II-Optimized version 5.03! thread for more details. Joe |
|
|
BrodoVolunteer tester
Send message
Joined: Feb 14 04
Posts: 364
Credit: 13,363,825
RAC: 56,105
|
|
Just a tip that some may find useful.
I found that altering the lines
<avg_ncpus>0.127970</avg_ncpus>
<max_ncpus>0.127970</max_ncpus>
back to the "stock" 0.05 gave smoother running on my CUDA box. This stopped a tendency to stall for periods of up to a minute on both GPU and CPU units and helped with VLAR's in particular.
Brodo |
|
|
|
|
|
This thread keeps getting buried. Just bringing it back to the front page.
____________
PROUD MEMBER OF Team Starfire World BOINC |
|
|
|
|
|
Following Brodo's comments about reducing avg/max_ncpus :-
I also had my settings as :-
<avg_ncpus>0.127970</avg_ncpus>
<max_ncpus>0.127970</max_ncpus>
I have been having issues with Computation Errors (exit code -5 = no result file) in the following circumstances with CUDA tasks - although I don't see any stalling going on.
1. When suspending a task, a new task starts and ends after about 6 seconds with error -5. A second task then starts OK.
2. When new tasks are downloaded at the top of the queue as the status changes to READY TO RUN it fails as above. The same continues to happen for all the following tasks as they arrive.
If I'm lucky and happen to spot a bunch of tasks like this before they get reported, I stop BOINC and change their states back to READY TO RUN and they then run OK.
On one PC I have now tried reducing the settings until I reached 0.099000 - problems at 0.100000. I haven't carried out exhaustive tests but was able to suspend tasks without new tasks erroring at this setting. I haven't yet seen if this reduction is throttling the GPU throughput.
I have been running AK V8 MB and stock CUDA app on versions of BOINC from 6.6.20 up to 6.6.28 on various PCs with GTS250 and GT8600 and GT9600 GPUs with various recent graphic driver versions. (GPUs not overclocked)
Has anyone else encountered similar problems?
____________
 |
|
|
Fred WVolunteer tester
Send message
Joined: Jun 13 99
Posts: 2175
Credit: 5,926,236
RAC: 19,577
|
Following Brodo's comments about reducing avg/max_ncpus :-
I also had my settings as :-
<avg_ncpus>0.127970</avg_ncpus>
<max_ncpus>0.127970</max_ncpus>
I have been having issues with Computation Errors (exit code -5 = no result file) in the following circumstances with CUDA tasks - although I don't see any stalling going on.
1. When suspending a task, a new task starts and ends after about 6 seconds with error -5. A second task then starts OK.
2. When new tasks are downloaded at the top of the queue as the status changes to READY TO RUN it fails as above. The same continues to happen for all the following tasks as they arrive.
If I'm lucky and happen to spot a bunch of tasks like this before they get reported, I stop BOINC and change their states back to READY TO RUN and they then run OK.
On one PC I have now tried reducing the settings until I reached 0.099000 - problems at 0.100000. I haven't carried out exhaustive tests but was able to suspend tasks without new tasks erroring at this setting. I haven't yet seen if this reduction is throttling the GPU throughput.
I have been running AK V8 MB and stock CUDA app on versions of BOINC from 6.6.20 up to 6.6.28 on various PCs with GTS250 and GT8600 and GT9600 GPUs with various recent graphic driver versions. (GPUs not overclocked)
Has anyone else encountered similar problems?
My experience is similar, but with significant variants. I have assumed that it is a "feature" of Boinc 6.6.23 so have not raised it as an issue - but since you ask...
I have <ave_ncpus> and <max_ncpus> both set to 0.15 and that has served me well so far.
If, for any reason, my rig goes into EDF mode (e.g. watching live-feed football on the web the other night so the GTX295 had other things to do for a change) whatever is being crunched at the time goes to "waiting to run" and 2 nearest scheduled WU's start up (this is ALL on the CUDA). When the first of those 2 finishes and uploads, the second goes into "waiting to run" and 2 new ones start up at the same time. And so it goes on - for every 2 that start, one reports and the second goes to "waiting to run" so when it comes out of EDF mode, I have a whole list waiting to run when their turn comes round.
Now the similarity - when those WU's finally do run, they error with the same exit code -5 = no result file.
So, as you can see, different circumstances - same symptom; perhaps there is a linkage somewhere?
F.
____________
|
|
|
|
|
|
I had mine at 0.127970 and was having no problems but saw it suggested that 0.040000 Would help it run a little bit smoother. I am trying it now but I don't see much change. Then again, I've never had the -5 problem either.(knock on wood)
____________
PROUD MEMBER OF Team Starfire World BOINC |
|
|
|
|
Now the similarity - when those WU's finally do run, they error with the same exit code -5 = no result file.
I got my first error -5 today, while doing some manual suspend/resume work to get a Beta test run to start before its time.
The full message is:
<core_client_version>6.6.28</core_client_version>
<![CDATA[
<message>
- exit code -5 (0xfffffffb)
</message>
<stderr_txt>
SETI@home error -5 Can't open file
(work_unit.sah) in read_wu_state() errno=2
File: ..\worker.cpp
Line: 123
</stderr_txt>
]]>
- so nothing to do with result files. [BOINC's message about a missing file is always a consequence of the crash, and says nothing whatsoever about the cause of the crash]
The behaviour of BOINC when suspending/resuming CUDA tasks does still seem to have some problems - I'll try to write it up for boinc_alpha.
Knowing the usual response - Fred, would you be willing to catch some debug logs and screen shots (of BOINC, not the footy) next time there's a good match on? |
|
|
|
|
I had mine at 0.127970 and was having no problems but saw it suggested that 0.040000 Would help it run a little bit smoother. I am trying it now but I don't see much change. Then again, I've never had the -5 problem either.(knock on wood)
There's nothing magical about 0.127970 either.
The figure was what BOINC worked out for my Q6600/9800GT combination when I was first experimenting with the new form of app_info files - see Beta message 36887. I think it probably comes from the SETI app needing about 2m 30s of CPU time for a task that runs 20 minutes on the CUDA card - the ratio feels about right.
So far as I know, the figure doesn't (shouldn't?) affect processing in any way: like the flops adjustment, it's supposed to be used just to smooth the work-fetch balance between CPU and CUDA tasks.
If you feel inclined to fiddle, I think you should try:
If you have a mega-fast CUDA card on a comparatively slow motherboard/CPU host, expect to use a higher<avg_ncpus> & <max_ncpus> figure.
If you have a fast CPU, but only a comparatively weak CUDA card, go the other way - use a lower<avg_ncpus> & <max_ncpus> figure.
But always keep both figures the same as each other.
(Unless you can work out something else that we don't know yet!) |
|
|
|
|
|
Unless of course you have a case like mine where everything is slow. :)
____________
PROUD MEMBER OF Team Starfire World BOINC |
|
|
Fred WVolunteer tester
Send message
Joined: Jun 13 99
Posts: 2175
Credit: 5,926,236
RAC: 19,577
|
Now the similarity - when those WU's finally do run, they error with the same exit code -5 = no result file.
I got my first error -5 today, while doing some manual suspend/resume work to get a Beta test run to start before its time.
The full message is:
<core_client_version>6.6.28</core_client_version>
<![CDATA[
<message>
- exit code -5 (0xfffffffb)
</message>
<stderr_txt>
SETI@home error -5 Can't open file
(work_unit.sah) in read_wu_state() errno=2
File: ..\worker.cpp
Line: 123
</stderr_txt>
]]>
- so nothing to do with result files. [BOINC's message about a missing file is always a consequence of the crash, and says nothing whatsoever about the cause of the crash]
The behaviour of BOINC when suspending/resuming CUDA tasks does still seem to have some problems - I'll try to write it up for boinc_alpha.
Knowing the usual response - Fred, would you be willing to catch some debug logs and screen shots (of BOINC, not the footy) next time there's a good match on?
Re-looking at my results, mine matches your result exactly, Richard.
Anything I can do to help, of course. I could even watch something other than soccer ;). What debug flags / screen-shots are needed?
F.
____________
|
|
|
|
|
Re-looking at my results, mine matches your result exactly, Richard.
Anything I can do to help, of course. I could even watch something other than soccer ;). What debug flags / screen-shots are needed?
F.
Jorden usually says "Run at least once with these flags on: <work_fetch_debug>, <sched_op_debug> and one run with <debt_debug>", but I think he's away this weekend, so we can make our own rules ;-)
Don't worry about work_fetch or debt_debug for this one: sched_op hardly seems to do anything. I think we're going to need <cpu_sched> and <cpu_sched_debug>.
For screenshots, I was thinking of those "every 2 that start, one reports and the second goes to 'waiting to run'" - something showing those 'waiting to run' on the tasks tab, perhaps with a matching later one showing the errors. |
|
|
Fred WVolunteer tester
Send message
Joined: Jun 13 99
Posts: 2175
Credit: 5,926,236
RAC: 19,577
|
Re-looking at my results, mine matches your result exactly, Richard.
Anything I can do to help, of course. I could even watch something other than soccer ;). What debug flags / screen-shots are needed?
F.
Jorden usually says "Run at least once with these flags on: <work_fetch_debug>, <sched_op_debug> and one run with <debt_debug>", but I think he's away this weekend, so we can make our own rules ;-)
Don't worry about work_fetch or debt_debug for this one: sched_op hardly seems to do anything. I think we're going to need <cpu_sched> and <cpu_sched_debug>.
For screenshots, I was thinking of those "every 2 that start, one reports and the second goes to 'waiting to run'" - something showing those 'waiting to run' on the tasks tab, perhaps with a matching later one showing the errors.
OK. I will give that a whirl tomorrow (should be watching the Spanish Grand Prix anyway). I've now upgraded to CUDA2.2 (and had to increase the GPU fan speed considerably) and BOINC 6.6.28 so, if it still happens it will prove that it is not driver or 6.6.23 causing it.
F.
____________
|
|
|
|
|
|
Well I've gone back and given this another go and am getting the same results as you are :-
<![CDATA[
<message>
- exit code -5 (0xfffffffb)
</message>
<stderr_txt>
SETI@home error -5 Can't open file
(work_unit.sah) in read_wu_state() errno=2
File: ..\worker.cpp
Line: 123
</stderr_txt>
Also get <status>-161</status> in the file_info section of client_state.xml which I use to track the errors and do a fix up.
Apologies for the "no result file" red herring. I think I had this problem mixed up with another issue I had.
I've also tried running with a few avg/nax_ncpus values ranging from 0.15 down to 0.04 on a Core 2 6600 / GT9600T (driver 18250) on Windows XP (not exhaustively).
I hadn't previously tried the lower settings but this seems on my set up to produce the same level of -5 errors when suspending as the
higher settings.
0.099 which seemed to be most reliable I found now does still give some -5 errors so it is hard to say what the full influences are.
Another thing I have noticed on just this machine is that some CUDA jobs occasionally hang and the elapsed and completed times continue to clock up into hours but progress doesn't move.
I don't think they are VLAR tasks (I have been doing a fairly coarse rebranding of those since I started getting flooded by them) and stop/starting BOINC kicks them into life again.
I also notice that some versions of app_info.xml in these threads give avg/max_ncpus = 1.000000 settings for the the non cuda apps.
My files do not have this entry. Is this significant or is it just for completeness and the 1.000000 the default setting anyway?
As I seem to be able to recreate the error -5s at will, I am happy to produce some debug output if it is of use.
John.
____________
|
|
|
|
|
|
I think I've worked out what's happening here, and I've submitted a bug report. Fred, you have mail (ISP permitting).
It seems likely to happen whenever a running CUDA task is pre-empted, and a new CUDA task started in its place. I think it will happen with every version of BOINC from v6.6.23 onwards, because of a bug with new code added then:
Changes for 6.6.23
- client: for coproc jobs, don't start a job while a quit is pending. Otherwise the new job may fail on memory allocation.
If the job start is delayed to allow the old one to tidy up after itself, the next attempt is treated as a re-start, instead of a new start: that's presumably why the work_unit.sah file isn't copied into the slot directory ready for use. |
|
|
|
|
|
I wasn't familiar with using the debug output so thought I'd have a go anyway out of interest. I assume that is what you were also seeing Richard?
1. When everything works OK after suspending a task, another one runs OK.
2. Sometimes an attempt to start a new task after a supend fails because the previous task has not exited (or it thinks it hasn't)
When this occurs however it has already changed the sched state of the task from 0 to 2.
When it does manage to run the task it does it as a resume not a start. As the task has never run previously you get
the error and it exits.
John
---------------------------------------------------------------------------------------------------------------------------------------
Here is a suspend that does not error :-
10-May-2009 20:17:07 [SETI@home] task 07fe09ab.14570.6207.11.8.131_1 suspended by user
10-May-2009 20:17:07 [---] [cpu_sched_debug] Request CPU reschedule: result suspended, resumed or aborted by user
10-May-2009 20:17:08 [---] [cpu_sched_debug] schedule_cpus(): start
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] scheduling 07fe09ab.14570.6207.11.8.151_1 (coprocessor job, FIFO)
10-May-2009 20:17:08 [---] [cpu_sched_debug] reserving 1 of coproc CUDA
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] highest debt: -3600.000000 07fe09aa.24575.16841.15.8.21_0
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] scheduling 07fe09aa.24575.16841.15.8.21_0 (CPU job, debt order)
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] highest debt: -7200.000000 01fe09ae.13226.25021.14.8.65_0
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] scheduling 01fe09ae.13226.25021.14.8.65_0 (CPU job, debt order)
10-May-2009 20:17:08 [---] [cpu_sched_debug] Request enforce CPU schedule: schedule_cpus
10-May-2009 20:17:08 [---] [cpu_sched_debug] enforce_schedule(): start
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] want to run: 07fe09ab.14570.6207.11.8.151_1
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] want to run: 07fe09aa.24575.16841.15.8.21_0
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] want to run: 01fe09ae.13226.25021.14.8.65_0
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] processing 07fe09aa.24575.16841.15.8.21_0
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] processing 01fe09ae.13226.25021.14.8.65_0
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] processing 07fe09ab.14570.6207.11.8.151_1
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] 07fe09aa.24575.16841.15.8.21_0 sched state 2 next 2 task state 1
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.75_0 sched state 1 next 1 task state 0
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.61_0 sched state 1 next 1 task state 0
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.72_0 sched state 1 next 1 task state 0
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.74_0 sched state 1 next 1 task state 0
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.31_1 sched state 1 next 1 task state 0
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] 01fe09ae.13226.25021.14.8.65_0 sched state 2 next 2 task state 1
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.129_1 sched state 1 next 1 task state 0
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.131_1 sched state 2 next 1 task state 1
10-May-2009 20:17:08 [SETI@home] [cpu_sched] Preempting 07fe09ab.14570.6207.11.8.131_1 (left in memory)
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.151_1 sched state 0 next 2 task state 0
10-May-2009 20:17:08 [SETI@home] Starting 07fe09ab.14570.6207.11.8.151_1
10-May-2009 20:17:08 [SETI@home] [cpu_sched] Starting 07fe09ab.14570.6207.11.8.151_1 (initial)
10-May-2009 20:17:08 [SETI@home] Starting task 07fe09ab.14570.6207.11.8.151_1 using setiathome_enhanced version 608
10-May-2009 20:17:08 [---] [cpu_sched_debug] enforce_schedule: end
10-May-2009 20:17:26 [---] Exit requested by user
10-May-2009 20:17:27 [---] [cpu_sched_debug] Request CPU reschedule: exit_tasks
---------------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------------
and here is one that does error from the point of suspend onwards :-
10-May-2009 20:33:18 [SETI@home] task 07fe09ab.14570.6207.11.8.135_1 suspended by user
10-May-2009 20:33:18 [---] [cpu_sched_debug] Request CPU reschedule: result suspended, resumed or aborted by user
10-May-2009 20:33:18 [---] [cpu_sched_debug] schedule_cpus(): start
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] scheduling 07fe09ab.14570.6207.11.8.234_0 (coprocessor job, FIFO)
10-May-2009 20:33:18 [---] [cpu_sched_debug] reserving 1 of coproc CUDA
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] highest debt: -3600.000000 07fe09aa.24575.16841.15.8.21_0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] scheduling 07fe09aa.24575.16841.15.8.21_0 (CPU job, debt order)
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] highest debt: -7200.000000 01fe09ae.13226.25021.14.8.65_0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] scheduling 01fe09ae.13226.25021.14.8.65_0 (CPU job, debt order)
10-May-2009 20:33:18 [---] [cpu_sched_debug] Request enforce CPU schedule: schedule_cpus
10-May-2009 20:33:18 [---] [cpu_sched_debug] enforce_schedule(): start
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] want to run: 07fe09ab.14570.6207.11.8.234_0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] want to run: 07fe09aa.24575.16841.15.8.21_0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] want to run: 01fe09ae.13226.25021.14.8.65_0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] processing 07fe09aa.24575.16841.15.8.21_0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] processing 01fe09ae.13226.25021.14.8.65_0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] processing 07fe09ab.14570.6207.11.8.234_0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09aa.24575.16841.15.8.21_0 sched state 2 next 2 task state 1
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.75_0 sched state 1 next 1 task state 0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.61_0 sched state 1 next 1 task state 0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.72_0 sched state 1 next 1 task state 0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.74_0 sched state 1 next 1 task state 0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.31_1 sched state 1 next 1 task state 0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 01fe09ae.13226.25021.14.8.65_0 sched state 2 next 2 task state 1
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.129_1 sched state 1 next 1 task state 0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.131_1 sched state 1 next 1 task state 0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.151_1 sched state 1 next 1 task state 0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.141_0 sched state 1 next 1 task state 0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.154_0 sched state 1 next 1 task state 0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.138_1 sched state 1 next 1 task state 0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.142_0 sched state 1 next 1 task state 9
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.135_1 sched state 2 next 1 task state 1
10-May-2009 20:33:18 [SETI@home] [cpu_sched] Preempting 07fe09ab.14570.6207.11.8.135_1 (removed from memory)
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.234_0 sched state 0 next 2 task state 0
**** state of new task 234 = 0 ****
10-May-2009 20:33:18 [---] [cpu_sched_debug] enforce_schedule: end
10-May-2009 20:33:18 [---] [cpu_sched_debug] coproc quit pending, deferring start
10-May-2009 20:33:18 [---] [cpu_sched_debug] Request enforce CPU schedule: coproc quit retry
**** unable to start new task 234 - last task not exited yet??? ****
10-May-2009 20:33:19 [---] [cpu_sched_debug] enforce_schedule(): start
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] want to run: 07fe09ab.14570.6207.11.8.234_0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] want to run: 07fe09aa.24575.16841.15.8.21_0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] want to run: 01fe09ae.13226.25021.14.8.65_0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] processing 07fe09aa.24575.16841.15.8.21_0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] processing 01fe09ae.13226.25021.14.8.65_0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] processing 07fe09ab.14570.6207.11.8.234_0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09aa.24575.16841.15.8.21_0 sched state 2 next 2 task state 1
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.75_0 sched state 1 next 1 task state 0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.61_0 sched state 1 next 1 task state 0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.72_0 sched state 1 next 1 task state 0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.74_0 sched state 1 next 1 task state 0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.31_1 sched state 1 next 1 task state 0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 01fe09ae.13226.25021.14.8.65_0 sched state 2 next 2 task state 1
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.129_1 sched state 1 next 1 task state 0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.131_1 sched state 1 next 1 task state 0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.151_1 sched state 1 next 1 task state 0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.141_0 sched state 1 next 1 task state 0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.154_0 sched state 1 next 1 task state 0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.138_1 sched state 1 next 1 task state 0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.142_0 sched state 1 next 1 task state 9
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.135_1 sched state 1 next 1 task state 8
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.234_0 sched state 2 next 2 task state 0
**** State of new task 234 now = 2 ****
10-May-2009 20:33:19 [---] [cpu_sched_debug] enforce_schedule: end
10-May-2009 20:33:19 [---] [cpu_sched_debug] coproc quit pending, deferring start
10-May-2009 20:33:19 [---] [cpu_sched_debug] Request enforce CPU schedule: coproc quit retry
**** Second attempt to restart task failed ****
10-May-2009 20:33:20 [---] [cpu_sched_debug] Request CPU reschedule: application exited
10-May-2009 20:33:20 [---] [cpu_sched_debug] schedule_cpus(): start
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] scheduling 07fe09ab.14570.6207.11.8.234_0 (coprocessor job, FIFO)
10-May-2009 20:33:20 [---] [cpu_sched_debug] reserving 1 of coproc CUDA
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] highest debt: -3600.000000 07fe09aa.24575.16841.15.8.21_0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] scheduling 07fe09aa.24575.16841.15.8.21_0 (CPU job, debt order)
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] highest debt: -7200.000000 01fe09ae.13226.25021.14.8.65_0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] scheduling 01fe09ae.13226.25021.14.8.65_0 (CPU job, debt order)
10-May-2009 20:33:20 [---] [cpu_sched_debug] Request enforce CPU schedule: schedule_cpus
10-May-2009 20:33:20 [---] [cpu_sched_debug] enforce_schedule(): start
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] want to run: 07fe09ab.14570.6207.11.8.234_0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] want to run: 07fe09aa.24575.16841.15.8.21_0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] want to run: 01fe09ae.13226.25021.14.8.65_0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] processing 07fe09aa.24575.16841.15.8.21_0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] processing 01fe09ae.13226.25021.14.8.65_0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] processing 07fe09ab.14570.6207.11.8.234_0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09aa.24575.16841.15.8.21_0 sched state 2 next 2 task state 1
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.75_0 sched state 1 next 1 task state 0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.61_0 sched state 1 next 1 task state 0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.72_0 sched state 1 next 1 task state 0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.74_0 sched state 1 next 1 task state 0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.31_1 sched state 1 next 1 task state 0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 01fe09ae.13226.25021.14.8.65_0 sched state 2 next 2 task state 1
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.129_1 sched state 1 next 1 task state 0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.131_1 sched state 1 next 1 task state 0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.151_1 sched state 1 next 1 task state 0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.141_0 sched state 1 next 1 task state 0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.154_0 sched state 1 next 1 task state 0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.138_1 sched state 1 next 1 task state 0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.142_0 sched state 1 next 1 task state 9
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.135_1 sched state 1 next 1 task state 0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.234_0 sched state 2 next 2 task state 0
10-May-2009 20:33:20 [SETI@home] [cpu_sched] Starting 07fe09ab.14570.6207.11.8.234_0(resume)
**** Third attempt -now trying to resume task 234 which has never run yet ****
10-May-2009 20:33:20 [SETI@home] Restarting task 07fe09ab.14570.6207.11.8.234_0 using setiathome_enhanced version 608
10-May-2009 20:33:20 [---] [cpu_sched_debug] enforce_schedule: end
10-May-2009 20:33:21 [---] [cpu_sched_debug] Request CPU reschedule: application exited
10-May-2009 20:33:21 [SETI@home] Computation for task 07fe09ab.14570.6207.11.8.234_0 finished
**** Task 234 exits without doing anything ****
---------------------------------------------------------------------------------------------------------------------------------------
____________
|
|
|
|
|
I wasn't familiar with using the debug output so thought I'd have a go anyway out of interest. I assume that is what you were also seeing Richard?
1. When everything works OK after suspending a task, another one runs OK.
2. Sometimes an attempt to start a new task after a supend fails because the previous task has not exited (or it thinks it hasn't)
When this occurs however it has already changed the sched state of the task from 0 to 2.
When it does manage to run the task it does it as a resume not a start. As the task has never run previously you get
the error and it exits.
John
Yes, that's exactly what I reported - both the change from sched state 0 to sched state 2, and the restart. |
|
|
Fred WVolunteer tester
Send message
Joined: Jun 13 99
Posts: 2175
Credit: 5,926,236
RAC: 19,577
|
I wasn't familiar with using the debug output so thought I'd have a go anyway out of interest. I assume that is what you were also seeing Richard?
1. When everything works OK after suspending a task, another one runs OK.
2. Sometimes an attempt to start a new task after a supend fails because the previous task has not exited (or it thinks it hasn't)
When this occurs however it has already changed the sched state of the task from 0 to 2.
When it does manage to run the task it does it as a resume not a start. As the task has never run previously you get
the error and it exits.
John
Yes, that's exactly what I reported - both the change from sched state 0 to sched state 2, and the restart.
I'm trying to work out why the completion of one EDF task on my GTX295 should shove the WU on the other core into "Waiting to tun" so that 2 new tasks can be started simultaneously (and that "Waiting to run" WU then loses its output file).
@Richard: You have mail - I can't make head nor tail of it but it may contribute another element to the eventual fix.
F.
____________
|
|
|
|
|
@Richard: You have mail.
Received and forwarded to the bug-reporting list. |
|
|
Fred WVolunteer tester
Send message
Joined: Jun 13 99
Posts: 2175
Credit: 5,926,236
RAC: 19,577
|
@Richard: You have mail.
Received and forwarded to the bug-reporting list.
Thank you. I guess I really ought to sign up.
F.
[edit]Creating that eMail sent my DCF from .23 to .64 resulting in another EDF and I now have 30+ WU's "Waiting to run" than will fail (if I don't abort them).[/edit]
[edit2]Another feature of this is that when the WU that is pre-empted is close to the end of crunching (as is often the case on my GTX295), the elapsed time recorded against it is close to full crunch-time. If it is a "shorty" - no checkpoint - it restarts from the beginning so the eventual crunch-time is double what it should be which kicks the DCF further out and prolongs the EDF mode. [/edit2]
____________
|
|
|
|
|
I think I've worked out what's happening here, and I've submitted a bug report. Fred, you have mail (ISP permitting).
It seems likely to happen whenever a running CUDA task is pre-empted, and a new CUDA task started in its place. I think it will happen with every version of BOINC from v6.6.23 onwards, because of a bug with new code added then:
Changes for 6.6.23
- client: for coproc jobs, don't start a job while a quit is pending. Otherwise the new job may fail on memory allocation.
If the job start is delayed to allow the old one to tidy up after itself, the next attempt is treated as a re-start, instead of a new start: that's presumably why the work_unit.sah file isn't copied into the slot directory ready for use.
Presumably its less likely to preempt tasks under 6.6.28 than 23. But still its an issue that needs to be addressed.
Richard I cross posted your message over at GPUgrid (hope you don't mind). A bunch of the guys over there are having issues with tasks aborting, possibly unrelated but you never know.
____________
BOINC blog
|
|
|
RaistmerVolunteer developer
Volunteer tester
Send message
Joined: Jun 16 01
Posts: 1016
Credit: 5,954,006
RAC: 12,572
|
|
Recived error:
11/05/2009 19:25:05 SETI@home [error] No app version for result: windows_x86_64 608
with :
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.04</max_ncpus>
<plan_class>cuda</plan_class>
<file_ref>
<file_name>MB_6.08_mod_CUDA_V11_VLARKill_refined.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>
What is wrong here ?? |
|
|
|
|
Recived error:
11/05/2009 19:25:05 SETI@home [error] No app version for result: windows_x86_64 608
with :
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.04</max_ncpus>
<plan_class>cuda</plan_class>
<file_ref>
<file_name>MB_6.08_mod_CUDA_V11_VLARKill_refined.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>
What is wrong here ??
Could it be because the platform is x86_64 and <file_name>MB_6.08_mod_CUDA_V11_VLARKill_refined.exe</file_name> is only for the x86? That's just a guess though. Other than that and not having the flop count it is exactly like mine.
____________
PROUD MEMBER OF Team Starfire World BOINC |
|
|
Fred WVolunteer tester
Send message
Joined: Jun 13 99
Posts: 2175
Credit: 5,926,236
RAC: 19,577
|
|
I would try it without the <platform> tag. I don't think it is contributing anything, anyway, as you are calling a 32-bit App.
F.
____________
|
|
|
|
|
|
BuMp.
____________
 |
|
|
 PappaForum moderator
Volunteer tester
Send message
Joined: Jan 9 00
Posts: 2115
Credit: 5,110,193
RAC: 9,101
|
|
Rob
there is not need to Bump as it is preserved in FAQ's, Astropulse, Cuda, MultiBeam - Read Only along with a link to this thread.
Regards
____________
Please consider a Donation to the Seti Project.
 |
|
|
|
|
|
I had the same problem just remove the _64 from the Platform Tag and all should be well.
Dave
____________
|
|
|
RaistmerVolunteer developer
Volunteer tester
Send message
Joined: Jun 16 01
Posts: 1016
Credit: 5,954,006
RAC: 12,572
|
|
Thanks all.
This stripped version works well now on my host (I crunch only MB on it for now).
<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8b_win_x64_SSSE3x.exe</name>
<executable/>
</file_info>
<file_info>
<name>MB_6.08_mod_CUDA_V11_VLARKill_refined.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<file_ref>
<file_name>AK_v8b_win_x64_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.04</max_ncpus>
<plan_class>cuda</plan_class>
<file_ref>
<file_name>MB_6.08_mod_CUDA_V11_VLARKill_refined.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>
</app_info>
|
|
|
|
|
|
I have just set up this pc to do Astropulse only using the Intel Opt APP
GenuineIntelIntel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz [x86 Family 6 Model 15 Stepping 11] (2 processors)
It is returning 2 results in around 15hrs each.
Question: Is there a reason why this is quicker than my i7 which is returning 8 results in around 20hrs each.
I realise that it may be because 1 or more of the i7 cores is feeding the Cuda apps but 5hrs is a big difference.
I believe I have the same AP Opt app running on both pc's (ap_5.03r112_SSE3.exe).
Should I run ssse4 app on the i7.
Thank's in advance.
Dave
____________
|
|
|
|
|
|
Check around Dave, you will see others have noticed the i7 as being slower though most are compared to Quads. It has to do with the hyperthreading ( basically running two WUs on one core). Though it takes you longer to do each WU, you are doing 8 to their 4. (or 2 in this case.)
____________
PROUD MEMBER OF Team Starfire World BOINC |
|
|
|
|
|
Thank's perryjay I have noticed that my times are similar to other i7's.
Would there be any advantage going to an ssse3 app instead of the sse3?
I have seen that the sse3 seems to be prefered?
Just noticed RAC of 30k thats a first.
____________
|
|
|
|
|
|
Dave, the ssse3 should give you a bit of a performance boost but I can't say exactly how much.
____________
PROUD MEMBER OF Team Starfire World BOINC |
|
|
|
|
|
OK thanks I will give it a try can't do any harm I Hope, touch wood.
I can always go back to sse3.
Cheers
____________
|
|
|
|
|
Dave, the ssse3 should give you a bit of a performance boost but I can't say exactly how much.
FYI...
There is no SSSE3 optimised app for Astropulse, only SSE3. |
|
|
|
|
|
Just been looking and came to that conclusion.
Thank's
____________
|
|
|
|
|
|
Sorry, forgot you said it was just doing APs.
____________
PROUD MEMBER OF Team Starfire World BOINC |
|
|
BrodoVolunteer tester
Send message
Joined: Feb 14 04
Posts: 364
Credit: 13,363,825
RAC: 56,105
|
|
This thread is too valueable to be lost in the archives - I see others have been looking for it so....
BUMP^
|
|
|
|
|
|
Very timely. The optimised Windows applications for Astropulse v505 have just been posted at Lunatics. Look for 'rev 168' for the new v505 compatible applications: the download packages also still contain r112 applications so you can help finish off the remnants of the previous run. A full multi-coloured announcement will no doubt follow when we can find Gecko_R7 (he's the only one with a key to the paint-spray closet ;-) ).
From what I've been able to read so far (not been successful in snagging a v505 on the main project yet myself), those running CUDA should put in the same flops value for v505/r168 as they did for v503/r112. I think this is a mistake by the project: the new stock application is considerably faster than the old stock application, so the estimates should have been changed - but for the time being, work with what you've got. |
|
|
|
|
Very timely. The optimised Windows applications for Astropulse v505 have just been posted at Lunatics. Look for 'rev 168' for the new v505 compatible applications: the download packages also still contain r112 applications so you can help finish off the remnants of the previous run. A full multi-coloured announcement will no doubt follow when we can find Gecko_R7 (he's the only one with a key to the paint-spray closet ;-) ).
From what I've been able to read so far (not been successful in snagging a v505 on the main project yet myself), those running CUDA should put in the same flops value for v505/r168 as they did for v503/r112. I think this is a mistake by the project: the new stock application is considerably faster than the old stock application, so the estimates should have been changed - but for the time being, work with what you've got.
As there is no SETI@home preference for v505 yet, does download of ap505 WUs rely on having 'If no work for selected applications is available, accept work from other applications?' selected or are they reusing the Astropulse option? (when there are some being sent out of course....)
____________
|
|
|
|
|
Very timely. The optimised Windows applications for Astropulse v505 have just been posted at Lunatics. Look for 'rev 168' for the new v505 compatible applications: the download packages also still contain r112 applications so you can help finish off the remnants of the previous run. A full multi-coloured announcement will no doubt follow when we can find Gecko_R7 (he's the only one with a key to the paint-spray closet ;-) ).
From what I've been able to read so far (not been successful in snagging a v505 on the main project yet myself), those running CUDA should put in the same flops value for v505/r168 as they did for v503/r112. I think this is a mistake by the project: the new stock application is considerably faster than the old stock application, so the estimates should have been changed - but for the time being, work with what you've got.
As there is no SETI@home preference for v505 yet, does download of ap505 WUs rely on having 'If no work for selected applications is available, accept work from other applications?' selected or are they reusing the Astropulse option? (when there are some being sent out of course....)
I think it will be considered v5
____________
come fly with us at TSWB. Turn off ASTROPULSE HERE
|
|
|
|
|
As there is no SETI@home preference for v505 yet, does download of ap505 WUs rely on having 'If no work for selected applications is available, accept work from other applications?' selected or are they reusing the Astropulse option? (when there are some being sent out of course....)
I think it will be considered v5
Not possible. The preference depends on the same ID in the database as what's listed on the Applications page. v5 and v505 are different applications, and since the preference for v505 has not yet been added the 'If no work for selected applications is available, accept work from other applications?' will be needed. Joe |
|
|
|
|
As there is no SETI@home preference for v505 yet, does download of ap505 WUs rely on having 'If no work for selected applications is available, accept work from other applications?' selected or are they reusing the Astropulse option? (when there are some being sent out of course....)
I think it will be considered v5
Not possible. The preference depends on the same ID in the database as what's listed on the Applications page. v5 and v505 are different applications, and since the preference for v505 has not yet been added the 'If no work for selected applications is available, accept work from other applications?' will be needed. Joe
Thanks Joe. I have that option ticked. I had them all ticked but have changed it temporarily to not include MB to see if I could get a 505. Seems like they are splitting a few more tonight although the current tape seems to have a lot of bad data. I'm guessing the network is maxed out again - nothing much moving at all although I did pick up a few 503 resends earlier. I assume they aren't actually creating any new 503s now?
Run only the selected applications
SETI@home Enhanced: no
Astropulse: yes
Astropulse v5: yes
If no work for selected applications is available, accept work from other applications? yes
Use Graphics Processing Unit (GPU) if available yes
Use Central Processing Unit (CPU) yes
____________
|
|
|
|
|
|
Will this 505 app be also included in the opti app. installer?
BR,
____________
 |
|
|
|
|
Will this 505 app be also included in the opti app. installer?
In due course, but it's not ready yet. Jason reckoned it should take at most a week from now. |
|
|
|
|
|
If tapes are being split as the server status shows,then why is is that even though I have all the boxes ticked to accept any work I am getting the Project has no jobs message.I was sent 1000 Cuda the other day but the schedular is not running them it is doing 2 Aqua cuda tasks that have a deadline of 2 months.
Are the tasks being sent to hosts that are nearer the server because thier pings are shorter?
Been like this for a couple of weeks.
____________
|
|
|
|
|
As there is no SETI@home preference for v505 yet, does download of ap505 WUs rely on having 'If no work for selected applications is available, accept work from other applications?' selected or are they reusing the Astropulse option? (when there are some being sent out of course....)
I think it will be considered v5
Not possible. The preference depends on the same ID in the database as what's listed on the Applications page. v5 and v505 are different applications, and since the preference for v505 has not yet been added the 'If no work for selected applications is available, accept work from other applications?' will be needed. Joe
Does anyone know when this option to select v505 will be added? |
|
|
BrodoVolunteer tester
Send message
Joined: Feb 14 04
Posts: 364
Credit: 13,363,825
RAC: 56,105
|
|
I've borked my app_info file :-(
I downloaded the new AP v5.05 package from Lunatics and pasted their app_info into my existing one. It was a straight paste and i was getting errors on starting the client so I did a little bit of trimming. When I start the client I get the following errors
[error] State file error: bad application name astropulse
[error] State file error: duplicate app version: astropulse_v5 windows_intelx86 503
My app_info is as follows
<app_info>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v505</name>
</app>
<file_info>
<name>ap_5.05r168_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<file_ref>
<file_name>ap_5.05r168_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse</app_name>
<version_num>500</version_num>
<flops>6743308755.375</flops>
<file_ref>
<file_name>ap_5.00r103_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<flops>7792267895.1</flops>
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8_win_SSSE3x.exe</name>
<executable/>
</file_info>
<file_info>
<name>setiathome_6.08_windows_intelx86__cuda.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx86</platform>
<flops>5244795698.625</flops>
<file_ref>
<file_name>AK_v8_win_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>0.05</max_ncpus>
<flops>2800000000</flops>
<plan_class>cuda</plan_class>
<file_ref>
<file_name>setiathome_6.08_windows_intelx86__cuda.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>
</app_info>
XML is NOT my forte, Can someone please tell me what's wrong ?
Thanks
Brodo
|
|
|
|
|
[error] State file error: bad application name astropulse
[error] State file error: duplicate app version: astropulse_v5 windows_intelx86 503
My app_info is as follows
<app_info>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v505</name>
</app>
<file_info>
<name>ap_5.05r168_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<file_ref>
<file_name>ap_5.05r168_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse</app_name>
<version_num>500</version_num>
<flops>6743308755.375</flops>
<file_ref>
<file_name>ap_5.00r103_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<flops>7792267895.1</flops>
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8_win_SSSE3x.exe</name>
<executable/>
</file_info>
<file_info>
<name>setiathome_6.08_windows_intelx86__cuda.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx86</platform>
<flops>5244795698.625</flops>
<file_ref>
<file_name>AK_v8_win_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>0.05</max_ncpus>
<flops>2800000000</flops>
<plan_class>cuda</plan_class>
<file_ref>
<file_name>setiathome_6.08_windows_intelx86__cuda.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>
</app_info>
You have two AstroPulse v5 sections: one at the beginning and one after v505. Remove the section in red and it should work.
____________
BOINC FAQ Service
BOINC & Optimized SETI download repository |
|
|
|
|
|
Good morning peoples.
5.20 am in the UK here, posting a question quickly before I go to work in the hope it'll be answered before I get home.
I'm currently running 2 systems. A Ph. II 955 with Boinc 6.6.36 and Raistmer's v9 opp apps, and a Ph. 9850 with the lunatics unified installer, again with Boinc 6.6.36. Both machines run cuda too, the 955 with a 9800GTX+, the 9850 with an 8600 GTS.
The 9850, in asking for work yesterday failed on downloading a v505 astropulse saying that it didn't have the correct info in app_info, whereas the 955 doesn't even ask for such work. I am currently running down the work on the 955 so that I can change over to the unified installer on this machine too. It's much easier than doing it manually. I had success setting up Raistmer's opp app on one machine, on the other I couldn't get it to work, so went with the unified installer. Go figure...
Has the v505 been optimized yet, and if it has, how can I add the information to my app_info to start doing the new work units? I'm happy to add it to both machines but I don't want to add it, then change it in a couple of weeks when an optimized app comes out if it's not been done yet.
Any info or help will be greatly appreciated.
[edit] I've seen the app_info in Ozz's previous post, would a cut and paste with the correct section be sufficient? [/edit]
Regards, Gizbar.
____________
--- I don't care what they say, seti or not. The answer is still 42 ! |
|
|
|
|
[error] State file error: bad application name astropulse
[error] State file error: duplicate app version: astropulse_v5 windows_intelx86 503
My app_info is as follows
<app_info>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v505</name>
</app>
<file_info>
<name>ap_5.05r168_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<file_ref>
<file_name>ap_5.05r168_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse</app_name>
<version_num>500</version_num>
<flops>6743308755.375</flops>
<file_ref>
<file_name>ap_5.00r103_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<flops>7792267895.1</flops>
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8_win_SSSE3x.exe</name>
<executable/>
</file_info>
<file_info>
<name>setiathome_6.08_windows_intelx86__cuda.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx86</platform>
<flops>5244795698.625</flops>
<file_ref>
<file_name>AK_v8_win_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>0.05</max_ncpus>
<flops>2800000000</flops>
<plan_class>cuda</plan_class>
<file_ref>
<file_name>setiathome_6.08_windows_intelx86__cuda.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>
</app_info>
You have two AstroPulse v5 sections: one at the beginning and one after v505. Remove the section in red and it should work.
Also remove the purple part, that's the other error. Joe |
|
|
BrodoVolunteer tester
Send message
Joined: Feb 14 04
Posts: 364
Credit: 13,363,825
RAC: 56,105
|
|
Worked a treat !!
Thanks Ozzfan and Joe for your help
Brodo |
|
|
|
|
[edit] I've seen the app_info in Ozz's previous post, would a cut and paste with the correct section be sufficient? [/edit]
As long as you also download the new AP v5.05 application as well, then yes, it would work.
____________
BOINC FAQ Service
BOINC & Optimized SETI download repository |
|
|
BrodoVolunteer tester
Send message
Joined: Feb 14 04
Posts: 364
Credit: 13,363,825
RAC: 56,105
|
|
From the top post in this thread
6. Browse your client_state.xml file (its in the BOINC data directory) and look for the entry <p_flops>. We need to use this number. Do NOT change this file.
7. Browse the BOINC log file to get the estimated speed of your GPU. This is usually given at the top of the log in Gflops. My 9800GT was estimated at 60Gflops.
8. For each of the apps multiply t |
