![]() ![]() I simply don't have the time (or inclination) to constantly retune boinc to my current workload, the above extension of the scheduling mechanism would serve to maximize (albeit course grained) the cycles I donate to boinc with minimal effort on my part. The schedule for my work Mac would, to a degree be a partial mirror image of the above. Ability to control the GPU usage during the scheduled times would be critical to optimizing boinc computational cycles. I'd like to be a say something like between 09 run on 100% of cpus at max of 100% cpu time and then between 18 run on 50% of cpus at a max of 50% cpu time and then between 01 run on 75% of cpus for a max of 50% of cpu time (this is when virus scans and disk main runs) and don't run in unspecified periods. It would be nice to have more control over the scheduling of work my personal MAC tends to sit awake (for boinc) during the day while I'm at work, in the evening my usage varies from light web surfing to heavy Java development. The daemon would on detecting AC Power would relaunch the (client/manager as appropriate) to resume normal processing and thus keep this user reasonably happy. This would allow the system (MBP Early 2011 ML 10.8.2) to switch the graphics card for better battery life. It would be nice if on detecting an "on batteries" condition if boinc (client/manager as appropriate) could fire up a lightweight daemon that simply monitors the power source and then cleanly exits. ![]() I'm only getting about 3-4hrs best case on battery. My normal configuration allows computing while on AC power only in the expectation that when on batteries the program will not draw down battery life clearly by locking the high performance graphics card this is not the case. The GPU did not switch to the internal HD3000 chip an boinc was listed as the blocking program, on shutting boinc down the GPU switch after a few seconds. I then started playing with the power connector to see what happens when going onto battery. Something I just noticed, like 20 minutes ago, I installed a program called gfxCardStatus which displays which GPU is in use & programs dependent on it. I abandoned it several years ago for the same reason and thought that in nearly TEN YEARS someone would have made an effort to make this easy to use ? I am so so exasperated listening to people I discuss this project with telling me they have abandoned it after a few days of trying to wrestle with the app. But what is the goal here ? Surely the goal is to involve as many people as possible ? I do know that there is limited money available and it is a volunteer project. It would appear as if the BOINC and Seti teams are doing their utmost to frighten off the global public, in order to leave the whole Seti etc projects to the nerds and techies. The interface is completely submerged in unintelligible tech terms and unintelligible preferences and options that compete between those set in the app and those set on the web. The interface is something you might expect in a college engineering course project. However I am posting here to say how appalled I am at the whole design/development of the Mac App. " for several weeks trying to solve my screensaver issues. have had a thread going over at "Number crunching : Waiting for more tasks. Hi all - I am parachuting in here - apols if I am in any way off topic. Turns out I've got to redo the machines with a clean install of 10.8, so I'll let you know. When we used Radmind, we didn't have these problems. I end up cloning from another machine, so that's pretty much where I start these days. I've never had good luck uninstalling and re-installing. ![]() The other 18? Only FSM knows for sure why things don't work. Two of the 20 are behaving properly regarding BOINC. I used to expect that clones would behave the same, but they don't. 19 of them are, in theory, exact clones of one machine (target disk mode is wonderful when one has an unreliable network that doesn't support netbooting). I moved the data folder as the very last step. When all else fails, I recommend running the Uninstall BOINC application that comes bundled with BOINC 7.0.31 for the Mac and then reinstalling. This may also apply when upgrading the OS. Maybe that's the problem.Remember that, since you are relocating the BOINC Data directory, you must create the symbolic link again each time you run the BOINC installer, as explained at the end of this section. Another wrinkle is that I had to do a "dirty" install of 10.8 over 10.6. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |