Message boards : Number crunching : Would this app_info.xml work?
Author | Message |
---|---|
I wrote an app_info.xml for long tasks. <app_info> <app> <name>GPUGRID</name> </app> <file_info> <name>acemdlong_6.15_windows_intelx86__cuda31</name> <executable/> </file_info> <file_info> <name>cudart32_31_9.dll</name> <executable/> </file_info> <file_info> <name>cufft32_31_9.dll</name> <executable/> </file_info> <file_info> <name>tcl85.dll</name> <executable/> </file_info> <app_version> <app_name>Long runs (8-12 hours on fastest card) (cuda31)</app_name> <version_num>615</version_num> <avg_ncpus>0.36</avg_ncpus> <max_ncpus>1.000000</max_ncpus> <plan_class>cuda31</plan_class> <coproc> <type>CUDA</type> <count>.5</count> </coproc> <file_ref> <file_name>acemdlong_6.15_windows_intelx86__cuda31</file_name> <main_program/> </file_ref> <file_ref> <file_name>cudart32_31_9.dll</file_name> <open_name>cudart32_31_9.dll</open_name> <copy_file/> </file_ref> <file_ref> <file_name>cufft32_31_9.dll</file_name> <open_name>cufft32_31_9.dll</open_name> <copy_file/> </file_ref> <file_ref> <file_name>tcl85.dll</file_name> <open_name>tcl85.dll</open_name> <copy_file/> </file_ref> </app_version> </app_info> Would this work? I'm running a Gianni task and the lowest reading in the last hour is 30% and the highest is 79%, with an average of 73%, checked with GPU-Z. The memory used is about 400MB. This way I could run like a SETI or MilkyWay wu with it to fully use the GPU. I know it slows down both WU's but my GPU gets fully utilized. And while running a Nathan which utilizes the GPU above 90% I would just change the <count> variable and restart BOINC. And how would the project administrators/developers/scientists feel about getting results from an 'anonymous platform'. Anthony. ____________ ![]() The longer I live, the more reasons I develop for wanting to die. | |
ID: 23533 | Rating: 0 | rate:
![]() ![]() ![]() | |
Is there a setting somewhere so that I only download 1 WU at a time. Or can I add a variable to the app_info so it will do that, for instance a very high flops number in the <flops> variable? | |
ID: 23534 | Rating: 0 | rate:
![]() ![]() ![]() | |
HI, | |
ID: 23536 | Rating: 0 | rate:
![]() ![]() ![]() | |
I want my GPU's to be fully utilized. If they are that means more work is done. | |
ID: 23537 | Rating: 0 | rate:
![]() ![]() ![]() | |
Optimizing is the way of the cruncher! | |
ID: 23542 | Rating: 0 | rate:
![]() ![]() ![]() | |
I run a GTX-570, a GTX-550TI and next week also 2 GTX-560TI-448's and an AMD HD6950 (all 3 in 1 system). | |
ID: 23544 | Rating: 0 | rate:
![]() ![]() ![]() | |
It will be interesting to see how you get on. | |
ID: 23547 | Rating: 0 | rate:
![]() ![]() ![]() | |
It's not all for GPUGrid. Maybe I'll try to get to 5M on GPUgrid, I want SETI and MilkyWay to get above 1M, maybe Einstein too, And then I'll see what I do. | |
ID: 23548 | Rating: 0 | rate:
![]() ![]() ![]() | |
There's an error in the app_info.xml file. When I update GPUGrid I get these messages: | |
ID: 23553 | Rating: 0 | rate:
![]() ![]() ![]() | |
With help from some guys at the BOINC forum I changed my app_info.xml to this: <app_info> <app> <name>acemdlong</name> <user_friendly_name>Long runs (8-12 hours on fastest card)</user_friendly_name> </app> <file_info> <name>acemdlong_6.15_windows_intelx86__cuda31</name> <executable/> </file_info> <file_info> <name>cudart32_31_9.dll</name> <executable/> </file_info> <file_info> <name>cufft32_31_9.dll</name> <executable/> </file_info> <file_info> <name>tcl85.dll</name> <executable/> </file_info> <app_version> <app_name>acemdlong</app_name> <version_num>615</version_num> <platform>windows_intelx86</platform> <avg_ncpus>0.36</avg_ncpus> <max_ncpus>1.000000</max_ncpus> <flops>167186362363.818660</flops> <plan_class>cuda31</plan_class> <api_version>6.7.0</api_version> <coproc> <type>CUDA</type> <count>.5</count> </coproc> <gpu_ram>402653184.000000</gpu_ram> <file_ref> <file_name>acemdlong_6.15_windows_intelx86__cuda31</file_name> <main_program/> </file_ref> <file_ref> <file_name>cudart32_31_9.dll</file_name> <open_name>cudart32_31_9.dll</open_name> <copy_file/> </file_ref> <file_ref> <file_name>cufft32_31_9.dll</file_name> <open_name>cufft32_31_9.dll</open_name> <copy_file/> </file_ref> <file_ref> <file_name>tcl85.dll</file_name> <open_name>tcl85.dll</open_name> <copy_file/> </file_ref> </app_version> </app_info> Now I need to test if this works. I'm not sure about the .dll files either. I don't now if they are executable. Anthony. ____________ ![]() The longer I live, the more reasons I develop for wanting to die. | |
ID: 23574 | Rating: 0 | rate:
![]() ![]() ![]() | |
Your GPU has 1GB and some of the long tasks use more graphics memory. | |
ID: 23578 | Rating: 0 | rate:
![]() ![]() ![]() | |
I've got the number from the client_state.xml file. I changed it in my own app_info.xml to 512 MB as you suggested. If anyone wants me to post the file with the changed value they can ask. | |
ID: 23579 | Rating: 0 | rate:
![]() ![]() ![]() | |
My app_info.xml works. Now I have to do some more testing to be sure utilization is 90%-99%, and test which application can do that best without errors. | |
ID: 23583 | Rating: 0 | rate:
![]() ![]() ![]() | |
To test performance you will need to compare completed 'same-type-tasks' that previously ran without the app_info file in place. You will also need to have identical system and Boinc settings. | |
ID: 23590 | Rating: 0 | rate:
![]() ![]() ![]() | |
With a Nathan unit I only see MilkyWay take the GPU to 99% utilization, with SETI and Einstein it stays lower. Don't remember the exact figures cause I tested it last night. It's running with a SETI unit now, and in the short moment I checked utilization stays within 77%-90%. | |
ID: 23595 | Rating: 0 | rate:
![]() ![]() ![]() | |
So the ram amount is how much each GPU card actually has or how much you're willing to allocate? (in the case of multiple identical GPUs...) | |
ID: 29217 | Rating: 0 | rate:
![]() ![]() ![]() | |
Yes <count>.5</count> means you are telling Boinc your card has 2 GPU's/to run two task on it. | |
ID: 29234 | Rating: 0 | rate:
![]() ![]() ![]() | |
Yes <count>.5</count> means you are telling Boinc your card has 2 GPU's/to run two task on it. Not quite. It's telling BOINC that each task will run on half a card. So, if you have one card, you can run two tasks on it: if you have two GPUs, you can run four tasks and so on. App_config.xml is certainly the easiest way to do this. You need at least BOINC v7.0.42 to use it: if you use v7.0.54 or later (the current alpha test version is v7.0.58) you can change the values and apply them ('read config file') while BOINC is running. | |
ID: 29235 | Rating: 0 | rate:
![]() ![]() ![]() | |
I wonder if anyone has given any thought to an option like Einstein has where you set this preference on the site (the so-called 'Dangerous' BRP option) Yes :) It hardly provides higher throughput at GPU-Grid and increases the averaged turn-around time - which is not something the project desires. Getting tasks back quickly is much more important to GPU-Grid than most (if not all) other projects. MrS ____________ Scanning for our furry friends since Jan 2002 | |
ID: 29241 | Rating: 0 | rate:
![]() ![]() ![]() | |
I think it's more likely the project would want one task to run over two GPU's than the other way round. | |
ID: 29250 | Rating: 0 | rate:
![]() ![]() ![]() | |
Message boards : Number crunching : Would this app_info.xml work?