Message boards : Number crunching : Does anyone have an app_config.xml that works?
Author | Message |
---|---|
Does anyone have an app_config.xml that works for GPUGRID? I'm running multiple machines with dual GTX690's, dual GTX590's, and two mixed machines with GTX690/660Ti, and GTX590/GTX660Ti. I would like to experiment with .5/gpu configurations to see if I could squeeze more work out of all this computing power. Thanks in advance to anyone/everyone who responds. Rick | |
ID: 31080 | Rating: 0 | rate: / Reply Quote | |
Try this one: | |
ID: 31081 | Rating: 0 | rate: / Reply Quote | |
I would like to experiment with .5/gpu configurations to see if I could squeeze more work out of all this computing power. Hi Rick. We've been through this extensively. Short answer: not a good idea. | |
ID: 31112 | Rating: 0 | rate: / Reply Quote | |
See this post just from this morning - doesn't seem like a good idea on typical long-run WUs. And you wouldn't want to run short-runs on this hardware, as long as any long-runs are left. | |
ID: 31115 | Rating: 0 | rate: / Reply Quote | |
Try this one: Thanks for the help CaptinJack, and the comments from the rest of you. I tried the app_config from your link and it does work. Based on your comments,rather than try to run multiple GPUGRIDs per processor, I'm trying to run grugrid ~ .7, and Other projects such as seti, Einstein, and Milkyway at ~ .3. Well see if this works, but with the first 24Hrs. under my belt, it seems to be worth the experiment. Rick ____________ | |
ID: 31121 | Rating: 0 | rate: / Reply Quote | |
Don't overburden the GPU with other apps or the time it takes the GPUGrid WU will increase dramatically. Going by GPU usage is a bad indicator, go by runtime, tasks returned/day and credit. Overall you might return more work or get better GPU credit running 2 tasks (1 GPUGrid and 1 at another light project), but when I tried more than 1 WU from another project the GPUGrid WU times increased massively (two or three times as long). You should also note that if you over-commit the CPU, GPU performance may be reduced exponentially. If for example you wanted to run POEM WU's + GPUGrid WU's on the same card don't use any more than 50% of the CPU cores. If you start seeing failures, all gains will be lost. | |
ID: 31123 | Rating: 0 | rate: / Reply Quote | |
I can confirm; a 30% reduction in GPU core allocation (from 1.0 to 0.7) results in a 100% increase in time required to complete a GPUGRID WU. Basically the same results on my GTX590's, GTX660Ti's, and GTX690's. I can't explain why, but that's what happened in my tests. Rick | |
ID: 31131 | Rating: 0 | rate: / Reply Quote | |
Hi Rick, | |
ID: 31225 | Rating: 0 | rate: / Reply Quote | |
Hi Rick, Wow, I was not expecting that behavior (50/50) in BOINC with a .7 GPU allocation to GPUGrid. I've run GUOPGrid with , Seti, Einstein, and Milkyway. All these other projects seem to benefit from sharing a GPU, that's why I was trying the same for GPUGrid. I'll continue to experiment, but it doen't look good. Thanks for the explanation MrS. Regards, Rick ____________ | |
ID: 31257 | Rating: 0 | rate: / Reply Quote | |
Actually I suspect this 50/50 only applies to running 2 similar WUs at once. Even for different WUs from GPU-Grid it probably differs. | |
ID: 31266 | Rating: 0 | rate: / Reply Quote | |
Ok, I'm getting wu's again, BUT I give up on what new app names to use in the app_config.xml file. Can anyone help me? Thanks in advance, Rick | |
ID: 32407 | Rating: 0 | rate: / Reply Quote | |
Ok, I'm getting wu's again, BUT I give up on what new app names to use in the app_config.xml file. Can anyone help me? Thanks in advance, Rick acemd.800-55.exe | |
ID: 32424 | Rating: 0 | rate: / Reply Quote | |
You can get the app_name by looking in the BOINC Manager Event Log for "Starting task" events. Following "using" is app_name. | |
ID: 32431 | Rating: 0 | rate: / Reply Quote | |
That was what I thought, but when I put "acemd.800-55.exe" or "acemd.800-55" or "acemd_800_55" and about 10 other variations, BOINC did not recognize the app name. Couriously, the new long app seems to accept the variables of the old "acemdlong" app name in my app_config.xml file. Rick | |
ID: 32508 | Rating: 0 | rate: / Reply Quote | |
You must use <name> of <app> section (=acemdlong, acemdbeta), not <name> of application. | |
ID: 32509 | Rating: 0 | rate: / Reply Quote | |
That was what I thought, but when I put "acemd.800-55.exe" or "acemd.800-55" or "acemd_800_55" and about 10 other variations, BOINC did not recognize the app name. Couriously, the new long app seems to accept the variables of the old "acemdlong" app name in my app_config.xml file. Rick I get the app names from looking in the client_state.xml file, within the <app> blocks. | |
ID: 32589 | Rating: 0 | rate: / Reply Quote | |
That was what I thought, but when I put "acemd.800-55.exe" or "acemd.800-55" or "acemd_800_55" and about 10 other variations, BOINC did not recognize the app name. Couriously, the new long app seems to accept the variables of the old "acemdlong" app name in my app_config.xml file. Rick Thanks Jacob. That's exactly what I was looking for. Regards, Rick ____________ | |
ID: 32827 | Rating: 0 | rate: / Reply Quote | |
No problem. <!-- GPUGrid.net --> <!-- GPU tasks do properly use higher process and thread priorities, compared to CPU tasks. --> <!-- GPU tasks sometimes use CPU sometimes don't, based on type of GPU task runs on. --> <!-- Recommend 1 gpu_usage, if user also has CPU projects. --> <!-- Recommend 0.001 cpu_usage, but might try 0.5, since if 2 are running, I KNOW the Kepler is using CPU --> <!-- Also might try 1 cpu_usage, so as not to overcommit per Task Manager's CPU Utilization --> <!-- Although x-at-a-time provides the best per-task-throughput, it ends up using a lot more CPU --> <!-- Switching to 0.4995, such that if an 8-CPU MT job is running, 2 GPUGrid jobs and 1 0.001 GPU job can all run together --> <!-- 0.5 cpu_usage so that 2+ GPU tasks will intentionally reserve at least 1 core --> <!-- 1.0 cpu_usage because, when SETI tasks run on 3rd GPU reserving a core, they still aren't getting enough CPU --> <app_config> <!-- Short runs (2-3 hours on fastest card) --> <app> <name>acemdshort</name> <max_concurrent>0</max_concurrent> <gpu_versions> <gpu_usage>1</gpu_usage> <cpu_usage>1</cpu_usage> </gpu_versions> </app> <!-- Long runs (8-12 hours on fastest card) --> <app> <name>acemdlong</name> <max_concurrent>0</max_concurrent> <gpu_versions> <gpu_usage>1</gpu_usage> <cpu_usage>1</cpu_usage> </gpu_versions> </app> <!-- ACEMD beta version --> <app> <name>acemdbeta</name> <max_concurrent>0</max_concurrent> <gpu_versions> <gpu_usage>1</gpu_usage> <cpu_usage>1</cpu_usage> </gpu_versions> </app> </app_config> | |
ID: 32831 | Rating: 0 | rate: / Reply Quote | |
Message boards : Number crunching : Does anyone have an app_config.xml that works?