Welcome to MilkyWay@home

Posts by Nightfire73

1) Message boards : Number crunching : GPUs with different compute capabilities in the same machine (Message 34292)
Posted 6 Dec 2009 by Nightfire73
Post:
Well thanks... but since those are NVIDIA GPUS I don't use the optimized app and therefore I don't have an app_info file.
You mean I should set up such a file and adapt it to the stock app?
2) Message boards : Number crunching : GPUs with different compute capabilities in the same machine (Message 33960)
Posted 29 Nov 2009 by Nightfire73
Post:
I have a box with 2x GTX260 and I recently added a 9800GT. The 9800GT, with compute capability 1.1, should not crunch MW WUs. But it does indeed, and it looks like it is slowing down one of the 260s.
Does anybody know how I can prevent the 9800GT from getting MW-WUs and use it only for other projects?
BTW when crunching other projects the 9800GT doesn't seem to affect the performance of the 260s.


29.11.2009 19:50:32 Processor: 4 GenuineIntel Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz [x86 Family 6 Model 23 Stepping 10]
29.11.2009 19:50:32 Processor: 6.00 MB cache
29.11.2009 19:50:32 Processor features: fpu tsc pae nx sse sse2 mmx
29.11.2009 19:50:32 OS: Microsoft Windows XP: Professional x86 Edition, Service Pack 3, (05.01.2600.00)
29.11.2009 19:50:32 Memory: 2.25 GB physical, 4.09 GB virtual
29.11.2009 19:50:32 Disk: 107.42 GB total, 55.52 GB free
29.11.2009 19:50:32 Local time is UTC +1 hours
29.11.2009 19:50:35 NVIDIA GPU 0: GeForce GTX 260 (driver version 19562, CUDA version 3000, compute capability 1.3, 896MB, 633 GFLOPS peak)
29.11.2009 19:50:35 NVIDIA GPU 1: GeForce 9800 GT (driver version 19562, CUDA version 3000, compute capability 1.1, 512MB, 308 GFLOPS peak)
29.11.2009 19:50:35 NVIDIA GPU 2: GeForce GTX 260 (driver version 19562, CUDA version 3000, compute capability 1.3, 896MB, 633 GFLOPS peak)
3) Message boards : Number crunching : Won't finish in time (Message 28236)
Posted 22 Jul 2009 by Nightfire73
Post:
Quod erat demonstrandum.
4) Message boards : Number crunching : Won't finish in time (Message 27772)
Posted 15 Jul 2009 by Nightfire73
Post:
I still maintain that people with overworked systems would be seeing these messages REGARDLESS of the BOINC version. While I don't dispute that 6.6.36 appears to have issues based on what a number of people are saying, it is not to blame for any and all issues in regards to people being told that their systems won't get work finished by deadlines


Brian, I agree with you. If our computers are overworked, we should get such messages (or no work) from all the projects and regardless of the boinc version.
And I can assure you, my computer is not overworked: The tasks all finish way before the deadline, and I do not get to see (ever) tasks running in high priority mode, contrary to what I see on other computers that may be turned off for some days and then go haywire when I turn them back on again. These are overworked indeed.
Now, if we want to see that there is an issue here and maybe try to find elements that help solve it, then I am more than happy to describe to the world what happens on my machines. But if the game is to blame all the overworked machines that suddenly turned up with the release of boinc 6.6.36, then I may go back to some previous version and crunch on happily as I did before with my overworked machine that does get all the jobs done in time, including MW.
I feel like a few years back, when I went to buy new tyres for my car. The guy in the tyre shop went on telling me that the size I was asking for did not exist and that it never was produced by any tyre manufacturer. I took him to the car, had him read the inscription on the side of my non-existent tyres, and went to buy the non-existent things elsewhere.
5) Message boards : Number crunching : Won't finish in time (Message 27713)
Posted 13 Jul 2009 by Nightfire73
Post:
Yeah, right... call me when 6.7. is ready.
6) Message boards : Number crunching : Won't finish in time (Message 27711)
Posted 13 Jul 2009 by Nightfire73
Post:
Hey folks... just installed 6.6.37. Now let's see what this one does...
;-))
7) Message boards : Number crunching : Won't finish in time (Message 27461)
Posted 10 Jul 2009 by Nightfire73
Post:
Thank you for your time and the explanations Bill.
Then I guess there must be something wrong in what the scheduler tells the server.
I checked again.... please tell me if I am wrong: I have 10 projects that run on 2 cores, which means I have 2x24 hours processing time a day, say 4.8 hours processing time per project per day (+ the cuda with 2 projects). So even with half that time I should be able to complete all the tasks way before the deadline. My cache is set to 0.5 days, so I usually have only 1 or 2 tasks per project waiting or running on my machine, and each projects gets equal resource share. I regularly get new work from all the projects, only MW sometimes comes up with the "won't finish in time" message. And this only with boinc 6.6.36. As an example, PrimeGrid has similar deadlines and similar running times, but I don't get strange messages from that server. Now my question is... did the earlier versions of boinc not understand that my comp is overworked, or (as I guess) is there something wrong with 6.6.36 that makes the MW server think my machine is overworked? Maybe the scheduler adds the cuda processing times to the equation, making the server believe there is not enough time for anoter MW task?
8) Message boards : Number crunching : Won't finish in time (Message 27334)
Posted 8 Jul 2009 by Nightfire73
Post:
Well ok, I run too many projects, but running only 2 doesn't solve the problem. Going back to an older version of boinc does.
Maybe I really don't understand the scheduling process. I thought, as you all confirm in your answers, that the scheduler decides how many tasks to get.
So if my comp is overworked, the scheduler should not request new tasks. Right?
But he does, and the server answers "won't finish in time".
How does the server know that new tasks won't finish in time?
Does the scheduler tell the server?
Let's assume the scheduler does tell the server that the tasks won't finish in time, so why does he ask for new ones if he already knows they won't finish in time?
Everything worked fine with 6.6.20. Now with 6.6.36 I am suddenly overworked.
U say the longer running times for the MW tasks pushed my machine over the edge. Does going back to 6.6.20 shorten the running times? Guess not, but everything works fine again.
I may also add that I used to run 12 tasks on an Athlon XP 2000 and never got overdue tasks, maybe because the scheduler did what it is supposed to do.
9) Message boards : Number crunching : Won't finish in time (Message 27156)
Posted 6 Jul 2009 by Nightfire73
Post:
I'm sorry if I do insist, but I really don't believe the problem resides in running 12 or 14 projects, or at least not the ones I run. MW is the only project with short deadlines, and when I get work, as I stated before, I get 2 to 4 WUs only, and I believe this is because Boinc "knows" that getting more would not allow them to finish in time. And so far that's ok. Of course, If I'd run less projects, I would get more MW WUs.
The real problem is that after completing the daily WUs for some days in a row, the project starts sending the "won't finish in time" message, although all the WUs completed in time (normally the same day, sometimes the next, but always way before the deadline). And I don't have any projects running in high priority either. After a few days I will eventually get new WUs, which will be crunched in time, only to see the ominous message appear again a few days later.
Resource allocation for all my projects is 7.69%, but i run FreeHal, which always runs as a non cpu intensive app, then I run GPUGRID, and that is handled by the GPU as well as SETI. So in the end I have only 10 projects running on the 2 CPUs, which means more than 4 hours crunching for each project every day. On top of that I use an optimized MW app, and WU times go from 30 minutes to 1.5 hours, which IMHO means that even if MW had a 1-day deadline I still should be able to get at least 2 WUs a day. So I don't really believe that the comp is overworked, and if it really was, then I would at least see the apps running in high priority mode, but they don't.
As John R. states, the problem appeared after installing Boinc 6.6.36. Everything worked fine before, and I used to run up to 16 projects at a time.
I believe the problem resides somewhere in the new Boinc version, or in its ability to communicate with the MW project. Now I am not one to go back to the old version and call it a day, because if everybody did so, the problems would never get solved.
10) Message boards : Number crunching : Won't finish in time (Message 27128)
Posted 5 Jul 2009 by Nightfire73
Post:
I have the same problem myself...
Boinc 6.6.36, Dual Core 2.66 GHz, 4 GB Ram, Asus ENGTS250 DK TOP.
I run 12 to 14 projects, including MW with an optimized app. When I get some MW WUs they all complete in time. Of course if I reset the project, I get like 15 WUs and after they are completed (going into high priority mode), I only get 2 to 4 WUs at a time, which is easily manageable. But then all of a sudden the "won't finish in time" message appears, and I don't get any WUs for some time.




©2024 Astroinformatics Group