Posts by Terminal123*

1) Message boards : Number crunching : de_plum_slice_EMD_NEW_100K error (Message 55012) Posted 4 Jul 2012 by Terminal123* Post: I'm getting the same results... 10 out of 10 failed. <core_client_version>7.0.25</core_client_version> <![CDATA[ <message> The system cannot find the drive specified. (0xf) - exit code 15 (0xf) </message> <stderr_txt> <search_application> milkyway_nbody 0.84 Windows x86_64 double OpenMP, Crlibm </search_application> Using OpenMP 4 max threads on a system with 12 processors Error reading histogram line 37: massPerParticle = 0.000100 09:34:59 (9072): called boinc_finish </stderr_txt> ]]>
2) Message boards : Number crunching : Errors in N-Body Simulation (Message 55009) Posted 4 Jul 2012 by Terminal123* Post: I've been getting alot of computation errors also recently (as in 10 out of 10 error) with the n-body milkyway @ home when I used to get hardly any as well. <core_client_version>7.0.25</core_client_version> <![CDATA[ <message> The system cannot find the drive specified. (0xf) - exit code 15 (0xf) </message> <stderr_txt> <search_application> milkyway_nbody 0.84 Windows x86_64 double OpenMP, Crlibm </search_application> Using OpenMP 4 max threads on a system with 12 processors Error reading histogram line 37: massPerParticle = 0.000100 09:34:59 (9072): called boinc_finish </stderr_txt> ]]>
3) Message boards : Number crunching : 7850/7870 (Message 54864) Posted 24 Jun 2012 by Terminal123* Post: If you want to have only MT WU's use your CPU and have the separations only crunch on your GPU's since it's way faster, the following is the app_info that I made and that I use. I can now crunch 3 WU's of the multi-threaded work units(4 cores per unit) and 4 of the GPU work units (2 units per card). I'm on 2x 7970's and I can pump out 4 GPU work units in total every 77 seconds. As per http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=2841 <app_info> <app> <name>milkyway</name> </app> <file_info> <name>milkyway_separation_1.02_windows_x86_64__opencl_amd_ati.exe</name> <executable/> </file_info> <app_version> <app_name>milkyway</app_name> <version_num>102</version_num> <flops>1.0e11</flops> <avg_ncpus>0.05</avg_ncpus> <max_ncpus>1</max_ncpus> <plan_class>ati14ati</plan_class> <coproc> <type>ATI</type> <count>0.5</count> </coproc> <cmdline>--gpu-target-frequency 10 --gpu-disable-checkpointing</cmdline> <file_ref> <file_name>milkyway_separation_1.02_windows_x86_64__opencl_amd_ati.exe</file_name> <main_program/> </file_ref> </app_version> <app> <name>milkyway_nbody</name> <user_friendly_name>MilkyWay@Home nbody Simulation</user_friendly_name> </app> <file_info> <name>milkyway_nbody_0.84_windows_x86_64__mt.exe</name> <executable/> </file_info> <file_info> <name>libgomp_64-1.dll</name> <executable/> </file_info> <file_info> <name>pthreadGC2_64.dll</name> <executable/> </file_info> <app_version> <app_name>milkyway_nbody</app_name> <version_num>84</version_num> <plan_class>mt</plan_class> <avg_ncpus>4</avg_ncpus> <max_ncpus>4</max_ncpus> <cmdline>--nthreads=4</cmdline> <file_ref> <file_name>milkyway_nbody_0.84_windows_x86_64__mt.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libgomp_64-1.dll</file_name> </file_ref> <file_ref> <file_name>pthreadGC2_64.dll</file_name> </file_ref> </app_version> </app_info>
4) Message boards : Number crunching : What ATI CCC versions runs OpenCL here? (Message 53946) Posted 7 Apr 2012 by Terminal123* Post: I've been using 12.3 on my 2x 7970's as well with no issues.
5) Message boards : Number crunching : app_info for separation on GPU and nbody on CPU (Message 53925) Posted 6 Apr 2012 by Terminal123* Post: Looks like my test was successful. It's now getting both separation and nbody's and it's running 3 nbody WU's at a time on 4 CPU cores each, and 4 separation WU's at a time on 2 Radeon HD 7970 video cards. This is pretty awesome. 7 Work Units at a time and it's spitting them out super fast as well.
6) Message boards : Number crunching : app_info for separation on GPU and nbody on CPU (Message 53924) Posted 6 Apr 2012 by Terminal123* Post: I'm still testing it, because so far it's only been getting CPU units...but then I changed my app preferences not to use CPU and then it finally got GPU work units, so now I've set it to get both and we'll see if it actually does.
7) Message boards : Number crunching : app_info for separation on GPU and nbody on CPU (Message 53923) Posted 6 Apr 2012 by Terminal123* Post: I ended up redownloading the 3 files from http://milkyway.cs.rpi.edu/milkyway/download/ and then restarted BOINC. It is now working and is using 4 CPU cores per work unit(runs 3 WU's simultaneously) of nbody and 2 wu's per gpu(runs 4 WU's simultaneously) Here is a copy of the app_info incase anyone else wants it: <app_info> <app> <name>milkyway</name> </app> <file_info> <name>milkyway_separation_1.02_windows_x86_64__opencl_amd_ati.exe</name> <executable/> </file_info> <app_version> <app_name>milkyway</app_name> <version_num>102</version_num> <flops>1.0e11</flops> <avg_ncpus>0.05</avg_ncpus> <max_ncpus>1</max_ncpus> <plan_class>ati14ati</plan_class> <coproc> <type>ATI</type> <count>0.5</count> </coproc> <cmdline>--gpu-target-frequency 10 --gpu-disable-checkpointing</cmdline> <file_ref> <file_name>milkyway_separation_1.02_windows_x86_64__opencl_amd_ati.exe</file_name> <main_program/> </file_ref> </app_version> <app> <name>milkyway_nbody</name> <user_friendly_name>MilkyWay@Home nbody Simulation</user_friendly_name> </app> <file_info> <name>milkyway_nbody_0.84_windows_x86_64__mt.exe</name> <executable/> </file_info> <file_info> <name>libgomp_64-1.dll</name> <executable/> </file_info> <file_info> <name>pthreadGC2_64.dll</name> <executable/> </file_info> <app_version> <app_name>milkyway_nbody</app_name> <version_num>84</version_num> <plan_class>mt</plan_class> <avg_ncpus>4</avg_ncpus> <max_ncpus>4</max_ncpus> <cmdline>--nthreads=4</cmdline> <file_ref> <file_name>milkyway_nbody_0.84_windows_x86_64__mt.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libgomp_64-1.dll</file_name> </file_ref> <file_ref> <file_name>pthreadGC2_64.dll</file_name> </file_ref> </app_version> </app_info>
8) Message boards : Number crunching : app_info for separation on GPU and nbody on CPU (Message 53922) Posted 6 Apr 2012 by Terminal123* Post: Although in looking closer..i'm missing the nbody file too...what the happened to them? Interesting...
9) Message boards : Number crunching : app_info for separation on GPU and nbody on CPU (Message 53921) Posted 6 Apr 2012 by Terminal123* Post: Does anyone have an app_info that will only process nbody on CPU and separations on GPU? I tried searching the forums and I cut and pasted different parts of other app_info's that I could find..but it doesn't appear to work. The errors I get are that pthreadGC2_64.dll and libgomp_64-1.dll don't exist. But it works with both just fine without using a custom app_info, so I'm sure it's just me making the app_info wrong. Does anyone have an app_info that would work in the way I describe? i7-3960x Extreme Edition 6 Cores(12 Logical) 2x Radeon HD 7970 3GB video Cards(need to be able to run 2 WU's per GPU)
10) Message boards : Number crunching : ready to report (Message 53808) Posted 27 Mar 2012 by Terminal123* Post: Assuming your network access is on, it'll periodically report them to get new tasks, or you can go ahead and select milkyway@home in your projects list and say "Update" - That will go on and report any completed.
11) Message boards : Number crunching : 6990 (Message 53787) Posted 25 Mar 2012 by Terminal123* Post: K Thanks for your help, I'll have to do some digging. My goal is to use my CPU for the n-body simulation, and my GPUs to run 4 of the separation tasks(2 per GPU) for maximum efficiency. They were completing 4 gpu work units in 120 seconds.
12) Message boards : Number crunching : 6990 (Message 53785) Posted 25 Mar 2012 by Terminal123* Post: Thanks! Although it appears the 100 work units I had just dissapeared. Do you have one that allows the milkyway@home n-body simulation to work as well? 3/25/2012 8:37:48 AM \| Milkyway@Home \| Message from server: Your app_info.xml file doesn't have a usable version of MilkyWay@Home N-Body Simulation.
13) Message boards : Number crunching : 6990 (Message 53783) Posted 25 Mar 2012 by Terminal123* Post: Alright, I made a new file and named it app_info without an extension, and restarted BOINC. How do I get it to load? It still is only using 2 WU's for 2 GPu's. C:\ProgramData\BOINC\projects\milkyway.cs.rpi.edu_milkyway is where I put it.
14) Message boards : Number crunching : 6990 (Message 53780) Posted 25 Mar 2012 by Terminal123* Post: Yea I was looking for the folder to put an app_info into but I didnt find it in my initial looking. If you can provide one to crunch multiple WU's per GPU, that would be awesome.. I noticed there's supposedly one in another thread but I wasnt sure if I should use it.
15) Message boards : Number crunching : Multi core support (Message 53776) Posted 24 Mar 2012 by Terminal123* Post: "However, AMD GPUs (not your's, only some high end models) can crunch these separation WUs within a minute, so you may consider running only n-body on your CPU to contribute efficiently." I have noticed this as well, however I haven't found a way to ONLY have the GPU do separation tasks and the CPU do only n-body simulation tasks. BOINC keeps downloading separation tasks as well as n-body for the CPU, and separation for the GPU. Do you know of a way?
16) Message boards : Number crunching : 6990 (Message 53775) Posted 24 Mar 2012 by Terminal123* Post: I have now set it to use at most 50% of cores, which is now keeping my overall CPU usage around 65-71% and the GU's are staying at 96-100% (Granted, they drop to 0 frequently since they're finishing work units so fast) From initial observations, it looks like they're now finishing them in 44 seconds instead of 50-60. The most recent 4 WU's finished in 44s, 44s, 44s, 44s. Also I would like to note that these GPU's are NOT overclocked at all. The top card is only at 69c@75% fanspeed, and the bottom card is at 57c@70% fanspeed. From research I've done, they can easily be bumped up on air to 1125Mhz and beyond instead of 925Mhz. They have great overclocking potential, I just haven't done it yet. I want to wait a few months.
17) Message boards : Number crunching : 6990 (Message 53774) Posted 24 Mar 2012 by Terminal123* Post: Actually, i just noticed that the GPU's werent getting enough assistance from the CPU's since I had 12 CPU WU's running and 2 GPU WU's running. I have since then changed max CPU's used to 90% and that allows 2 to stay free to assist the GPU more. The GPU Usage was only 60-85% before, now it's 85-96%. I'm going to test freeing up another CPU core so the GPU's can operate at 100% GPU usage and I'll let you know the results.
18) Message boards : Number crunching : 7970 crunching more WUs (Message 53772) Posted 24 Mar 2012 by Terminal123* Post: I changed this to 10 instead of 60, and don't seem to notice a difference...Is there something specific I'm looking for? One thing I do notice, is that my GPU's are only fluxuating between a 65-80% load when 12 CPU Cores are crunching 12 WU's and my 2 GPU's are crunching 2 WU's. But if limit it from 100% cpu's used to 10%, it will run 2 GPU WU's and 1 CPU WU and my GPU's will be at 95-100% load, and finish units faster. So I think what I'm running into is that the 2 GPU WU's are needing some CPU assistance, but since they're all busy crunching of their own, there's not enough left over. I see that you can set a max number of cores used, but can you specific 11 CPU cores and 2 GPU? Edit: It looks like the sweet spot is to set it to use 90% of cores, that way it uses 10 CPU and 2 GPU, allowing the 2 extra CPU cores to assist in the 2 GPU WU's. I'm currently crunching with the following: CPU: i7-3960x @ Stock Speeds RAM: 32GB of Quad Channel 2133Mhz GPU1: Radeon HD 7970 3GB @ Stock Speeds GPU2: Radeon HD 7970 3GB @ Stock Speeds
19) Message boards : Number crunching : 6990 (Message 53771) Posted 24 Mar 2012 by Terminal123* Post: I'm currently crunching with the following: CPU: i7-3960x @ Stock Speeds RAM: 32GB of Quad Channel 2133Mhz GPU1: Radeon HD 7970 3GB @ Stock Speeds GPU2: Radeon HD 7970 3GB @ Stock Speeds On Average, each work unit is completing between 50-60 seconds.(GPU WU) So if you want to see how these components perform with Milkyway@home you can look at my tasks. Something I'm curious of, is if there's a way to have only my GPU's do the crunching since they take 55-60 seconds per WU, yet the 1.00 CPU WU's take around 6000 seconds(Granted, it can run 12 WU's at a time so about every 500 seconds I'm completing a CPU WU)