Questions and Answers :
Windows :
What do i need to run MooWrapper?
Message board moderation
Previous · 1 · 2
Author | Message |
---|---|
Send message Joined: 3 May 11 Posts: 16 Credit: 300,002,061 RAC: 0 |
|
Send message Joined: 20 Apr 11 Posts: 388 Credit: 822,356,221 RAC: 0 |
i'll test a little more Sure, and please let us know if you keep having problems. I wouldn't want people to find it too hard to contribute for our project. :) BTW, I did some investigations on my own host (this one http://moowrap.net/results.php?hostid=1&offset=0&show_names=0&state=3&appid=) yesterday while trying to optimize my clock speed and cooling. I found out that setting the core to 3 from the default 0 does decrease the CPU reported (as shown on Task Manager) by the app but it also affected GPU utilization. I now set the core to zero (actually letting it to default to that) which made my GPU usage to be around 97-100% on all three cards. It also doesn't take that much CPU unless there's throttling or over heating of VRMs (makes the card to jump into different speed to cool things down). These seem to also increase the communication between GPU and CPU, which is understandable. Normally CPU peaks only when next packet is loaded on a GPU and if all three card switch at same time, it's a bit bigger peak. I would recommend using utility like GPU-Z (see http://www.techpowerup.com/downloads/SysInfo/GPU-Z/) to check for temperatures and GPU usage figures for your cards while trying to figure things out. So, all in all, it can be complicated to set everything so that you get optimum crunching but also not to affect your daily usage. :) -w |
Send message Joined: 3 May 11 Posts: 16 Credit: 300,002,061 RAC: 0 |
on this host http://moowrap.net/show_host_detail.php?hostid=298 i crunch for about a week. Only MooWrapper and funny thing, is the WU lenght change ? the typical Run time(sec) was about 1700 (1,781.63, 1,709.41) so more or less under 30min http://moowrap.net/result.php?resultid=1316975 http://moowrap.net/result.php?resultid=1316974 and today I've got all 1h task http://moowrap.net/result.php?resultid=1316519 http://moowrap.net/result.php?resultid=1316518 http://moowrap.net/result.php?resultid=1316516 so double the time, same amoung of pts so what has change ? Join us at www.boincatpoland.org |
Send message Joined: 12 Jul 11 Posts: 112 Credit: 229,191,777 RAC: 0 |
Hello all..Just joined Moo and noticed on my i7, 64W7 w/5870 they take 2000/6000 sec to finish a wu. My AMD x4, 32WXP w/5870 avg. 1200 sec. If I looked in the right place, all wu's 32 bit? All Boinc 6.12.33 no OCing. |
Send message Joined: 5 May 11 Posts: 233 Credit: 351,414,150 RAC: 0 |
The timings for the i7 vary wildly, there should not be *that* much difference between the machines as both run 5870s. The AMD machine is very consistent within a few seconds. At a guess .... looks like you are running CPU WUs on all cores on the i7 ??. If so, and they are not multi-thread, run them on four cores to start with see how it goes, probably will be able to get to 5 cores in the end once you look at performance, leaving one core "free" to support the gpu. If its a multi thread CPU WU, then it will take all cores it finds (usually), in that case decision time .... GPU WUs or that particular CPU WU. It varys hugely, and is dependent on the CPU WU/multitheread/single thread/efficiency of CPU app - but they can monopolise the CPU causing brief wait states where the GPU waits for a space to get "serviced" by the CPU. That would account for the varying GPU times. Watching a movie or running a game at the same time would have the same varying effect. You gain more by freeing up a core for supporting the GPU, than lose by stopping CPU WU on one core. If thats not it, please post again with any other symptoms, as you should not be getting the varying times on the i7. EDIT: Scratching my head on this .... even a CPU WU clash shouldnt really be doing this, to this this extent, on the AMD..... there is a setting in preferences that controls CPU useage (in Preferences - Processor Useage - look at "While processor useage less than"). That setting defaults to 25% on install. That means if the CPU useage goes above 25% on non BOINC tasks, BOINC shuts down the CPU (and therefore GPU as well) until it detects useage going back down below 25%. Its a real pain, and if this is the case, set it to zero percent (which gives BOINC unrestricted access to the CPU, and the GPU will not shut down) . BOINC backs off anyway if it detects non BOINC calls for CPU. You have a chunky i7, so the minor side effects of zero percent will not affect you. Regards Zy |
Send message Joined: 12 Jul 11 Posts: 112 Credit: 229,191,777 RAC: 0 |
Both machines are set up to run 24/7/365. No gaming, surfing, just pure crunching with weekly defrag and cleaning. Nothing in the settings to inhibit crunching, set to full crunching. One of the things might be is I still have PPS ATI wu's on both machines. I throw in 2/3 PPS wu's here and there to get them crunched before DL. Both rigs crunching PPS cpu wu. When Aqua can get it together ill go back to them. I can reduce my cpu usage to free up a cpu and try that but with Aqua being multi threaded it might not work. |
Send message Joined: 5 May 11 Posts: 233 Credit: 351,414,150 RAC: 0 |
Yup, with Aqua as its a multi-thread app, its all or nothing, you cant split down the cores. Bit of a lame comment I am aware ... however ... there is a marked difference between the i7 and the AMD machine. The i7 is all over the place, so there has to be something with the i7 setup itself, the cpu apps it deals with, or -and this is a long way away yet, dont overeact to the statement - there is the possibility there is a hardware failure lurking. I'd suspend all CPU WU activity, run the 5870s at the same settings on both machines - then see what happens. A "level playing field" in terms of setup and run settings should hightlight more whats happening. Regards Zy |
Send message Joined: 20 Apr 11 Posts: 388 Credit: 822,356,221 RAC: 0 |
Yes, only 32-bit apps on Windows but I hope to get a 64-bit version compiled. As to the run time differences, two things come to mind. First is CPU starvation and second is overheating causing the card to throttle itself. You can try to solve first problem by switching to core 3 or making sure there's no normal priority process demanding CPU. I'll probably try bumping the CPU priority in the next app version which might help. Second is trickier but you can at least verify if this is the case with monitoring the Mhz and temperature of the card using a utility like GPU-Z. Especially the VRM lines get overheated for me (but that's on a 5970). An external utility throttling the card can also have this affect on performance (and possibly demand more CPU). -w |
Send message Joined: 20 Apr 11 Posts: 388 Credit: 822,356,221 RAC: 0 |
and funny thing, is the WU lenght change ? Oh, wow, looking at the results, it seems that host lost about 1000Mkeys/sec (normally does 1900Mkeys/sec but was going 900MKeys/sec at worst) and that counts for the slowdown in crunch rate. The work units are a bit bigger (12 packets was increased to about 15 packets) but bigger ones would give more credits. However, looks like things are better recently so it must have been a temporary slowdown? This slowdown could haven been due to overheating, external throttling or CPU bottleneck (like high CPU on a normal priority process). -w |
Send message Joined: 2 May 11 Posts: 53 Credit: 255,380,797 RAC: 8,740 |
I run 2xATI 5870 in each of two AMD Phenom machines (one x4 and one x6), both on Win XP 32 bit. My run times on Core #0 was anywhere from 950 sec (15.8 min) to 2,200 sec (36.6 min) on either machine, I have not worked out why the different run times or if it was when I was using the machine for something else at the times of the long run times. The majority of times are around 1,080 sec (18 min) to 1,320 sec (22 min). A day or so ago I changed to Core #3 and so far my run times have been from 850 sec (14.2 min) to 1900 sec (31.7 min) with the majority of times around 1,020 sec (17 min) to 1,260 sec (21 min). So a little better but not all that much. It would also appear in my case that running out of memory or at least running low on available memory can make a huge difference in run times. When running up to 3 or 4 Yoyo Euler work units or Ralph work units or Cosmology work units, which are all memory hungry programmes, my computers become slow or unresponsive and consequently ALL work units, be they CPU or GPU, would slow right down and take up to double the normal run times. This is the reason I think for my long GPU run times. This may be of help for others. Conan |
Send message Joined: 12 Jul 11 Posts: 112 Credit: 229,191,777 RAC: 0 |
GOOOOD...my 5870 is working here now! I was having long run times, 1:30:00, on my i7 950 W7 64, Now avg. 35 min. Do not know why? I ran just Moo and played with the Moo core, no cpu'ing. Anyway its running and thats great! My AMD is still crunching great also... |
Send message Joined: 2 May 11 Posts: 53 Credit: 255,380,797 RAC: 8,740 |
I found that I had to change the Core back from #3 to #0 as it was causing one computer to run slow but the other to run a little bit faster. Back at Core #0 the times are speeding up on one machine and staying where they were on the other, in other words back to normal for me. Conan |
Send message Joined: 3 May 11 Posts: 16 Credit: 300,002,061 RAC: 0 |
LOL works for me as well :) It worked on #3 core, for about 2weeks with no problems. And now it needs to be change to #1 core to work again :) No OC, no changes on hardware, no updates, no CPU work, nothing has change :) Join us at www.boincatpoland.org |
Send message Joined: 3 May 11 Posts: 16 Credit: 300,002,061 RAC: 0 |
|