Concerning the memory reported for my gpu's
Concerning the memory reported for my gpu's |
|
| log in |
Questions and Answers : GPU applications : Concerning the memory reported for my gpu's
Previous · 1 · 2
| Author | Message |
|---|---|
07-Sep-2012 16:25:16 [SETI@home] Sending scheduler request: To fetch work. Addendum to TNG's post: You don't see how much work BOINC is asking either, as that's considered confusing information these days by the BOINC developers. So you'd have to add a cc_config.xml file and add into it: <cc_config> <log_flags> <sched_op_debug>1</sched_op_debug> </log_flags> </cc_config> Save it into /etc/boinc-client when using the package maintained version. Save it into /your home/BOINC/ directory when using Berkeley's BOINC. Next open BOINC Manager->Advanced view->Advanced->Read config file. Now the log will show how much work is being asked. Then you'll see it do things like this: example from my system, for Einstein work for my ATI GPU wrote: 28/09/2012 02:52:55 | Einstein@Home | [sched_op] Starting scheduler request And (hypothetically) if you were to delete the Lunatics application and try to do this with your BOINC with all default stock applications, you'd see that on the work request there'd be a request for 1 second for the Nvidia card. ____________ Jord - BOINC FAQ Service - BOINC User Wiki Real is just a matter of perception. | |
ID: 1288783 ·  | |
|
those first 5 errors (code22) are cpu work that failed instantly. it was an attempt to use another optimized cpu application, (ak-v8-ssse3) that didn't go so well. Ageless wrote: The GPU application is 32bit. The application I downloaded and installed "said" 64 bit, is it ? app : Lunatics_x41g_linux64_cuda32 I did have to install some dependency stuff to get Boinc 7.0.33 to work initially , xscreensaver libs and opensuse (these packages provided the missing libs that boinc was unable to find) Random thoughts : gpu "2" was chossen by boinc on all failed gpu work , but not all gpu work sent to gpu2 failed. only the files with very short estimated time errored. Disabling gpu2 with cc.config seemed to stop the errors however I have 2 gpus I'd like to have them both working. I had a heck of a time with syntax errors in every "provided" app.info.xml that was distributed with the optimized apps , I had to add a few close tags and change some spacing before boinc would read it (btw I tried several app.info files that were supposedly copy/paste-able.) so heres a valid question , is there a more in-depth faq or guideline for writing a app.info.xml ? ... I have the right idea how it goes but am not sure about where to define the version between the 528 and 603 SAH stock cpu app More specifically, what purpose is the <app> line ? is that to enclose an app of similar name that may have more than one version? Should it be used for each app section (sah , AP , CUDA_FeRMI) ? output from ldd for x41cuda app : ldd wrote: zotacii@zotacii-desktop:/home/BOINC/projects/setiathome.berkeley.edu$ ldd setiathome_x41g_x86_64-pc-linux-gnu_cuda32 the two files "not found" ARE present in the projects/sah folder .. do they need to be somewhere else? Does this look right? (I want to add the gpu apps and optimized cpu astropulse while retaining the stock multi-band cpu apps) app.info.xml wrote: <app_info> | |
| ID: 1288983 · | |
the two files "not found" ARE present in the projects/sah folder .. do they need to be somewhere else? Do those two files have the executable bit set? Gruß, Gundolf | |
| ID: 1289063 · | |
|
Sorry, I missed that those were CPU tasks. Not awake yet. :)
Hmmm, as far as I know all GPU apps are 32bit. I think this is because the Lunatics app requires that the CPU has SSE3, which all 64bit CPUs and only a handful of 32bit CPUs do. It also shows that in the actual application name: setiathome_x41g_x86_64-pc-linux-gnu-cuda32; Setiathome, x41g is an instruction set specifically for Nvidia GPUs, x86_64 is 64bit CPU (as opposed to intelx86, which is 32bit CPU), PC (as opposed to Mac), Linux, GNU is "GNU's Not Unix!", the GPU requires CUDA 3.2 and above drivers. All GPU applications actually run on the CPU, but none need a memory access of more than 4GB, or be able to address that amount of space, so it's really not necessary to make a specific 64bit application. What about videocards with 4GB and more of memory on them? Also not necessary that the application is 64bit, as the application doesn't address memory on the videocard, it just translates the task to kernels that the GPU can read, then transports those kernels to the GPU, which computes them, then the outcome is transported back to the PC, translated by the CPU back into something the humans can read, written to disk and the cycle repeats itself. so heres a valid question , is there a more in-depth faq or guideline for writing a app.info.xml ? Well, first off it's an app_info.xml file, just as it is a cc_config.xml file. It's an underscore _ not a dot . Check out Anonymous platform in the BOINC Wiki User Manual for more information. More specifically, what purpose is the <app> line ? It's to enclose the name of the main application that you're specifying in the sections thereafter. setiathome_enhanced and astropulse are the main applications. libcudart.so.3 => not found These two files are part of the Lunatics package that you installed in that directory. They're copied to the correct slot when the task runs. However, BOINC will also try to find the libcudart.so file on startup, it's how it detects if your GPU is CUDA capable. The videocard drivers install this file in this instance. So it should be elsewhere on your system as well, albeit possibly a different version than the one in the Lunatics package. They add it for complete compatibility with their application, as they used these files when they compiled their application. You app_info.xml file I'll leave to someone else to look over. ____________ Jord - BOINC FAQ Service - BOINC User Wiki Real is just a matter of perception. | |
| ID: 1289067 · | |
the two files "not found" ARE present in the projects/sah folder .. do they need to be somewhere else? They do and the above app_info.xml loaded flawlessly so I assume that means it's right :P | |
| ID: 1289093 · | |
|
ok , so up and running again, one gpu ignored... still making more errors than success 60/40 recent error wrote:
what can i use to test video ram within linux? | |
| ID: 1289107 · | |
|
https://simtk.org/home/memtest has MemtestG80 and MemtestCL: Memory Testers for CUDA- and OpenCL-enabled GPUs for Linux and Windows. | |
| ID: 1289109 · | |
|
Memory was fine. | |
| ID: 1292124 · | |
Questions and Answers : GPU applications : Concerning the memory reported for my gpu's
| Copyright © 2013 University of California |
