Posts by Richard Kimber

1) Questions and Answers : Unix/Linux : CPDN badly behaved (Message 42227) Posted 21 May 2011 by Richard Kimber Post: I'm running CPDN and other projects on Ubuntu 11.04 with Boinc 6.10.59. The machine is AMD Phenom II x4 945. My preferences are that up to three CPUs may be used by Boinc projects. I have just had a CPDN work unit that wanted to run high priority. By doing this it took over the entire Boinc allocation, presumably for the next couple of months, but only ran in one CPU, thus preventing other projects from working at all and leaving two CPUs unused. Is there a way of getting CPDN to work in a more friendly fashion? I have aborted the work unit concerned.
2) Questions and Answers : Unix/Linux : limiting number of simultaneous work units (Message 40703) Posted 17 Sep 2010 by Richard Kimber Post: Thanks for your helpful advice.
3) Questions and Answers : Unix/Linux : limiting number of simultaneous work units (Message 40692) Posted 17 Sep 2010 by Richard Kimber Post: If you just let Boinc do its own thing and take these decisions for itself it will do all these things. It's designed to be left alone with no user intervention. However, if the scheduler finds itself with a big load of climate models that need to be completed by a particular date, it may decide that the best way to fulfil all those goals is to run the climate models first. Let it do that. Your Boinc scheduler will then work out for itself that over the long term it's allocated too much time to CPDN and not enough to your other projects. CPDN has accumulated a debt. The scheduler will then, as soon as it can, give extra time to the other projects to even up their relative debts. In the long term you will find that Boinc will give the exact resource share to each project that you wanted. This could mean Boinc refusing to download new CPDN work for a while. It honestly doesn't matter if Boinc gives more time to CPDN for a while and later gives lots of time to, say, Seti. Thanks for your reply, and I now see what Boinc is trying to do. However, I prefer a more even style of work. As things stand, it seems I could spend a couple of months on high priority climate models at the expense of projects that take maybe an hour, and find that when the climate models are done there's no work available on the other projects. I guess your suggestion of suspending one of the climate models is the answer. Though I think it would be much better if the user could control the number of models per project.
4) Questions and Answers : Unix/Linux : limiting number of simultaneous work units (Message 40686) Posted 16 Sep 2010 by Richard Kimber Post: I'm not sure I can see anything called a 'cache limit', but in my general Boinc preferences I have 'Maintain enough work for 0.25 days'. Is this it? If so, I'm getting two work units despite that. I get more than one WU for other projects, but it's not a problem because the computation time is small in relation to the deadline. By aborting one of the climate units, the other ceases to run at high priority, and everything is normal.
5) Questions and Answers : Unix/Linux : limiting number of simultaneous work units (Message 40682) Posted 16 Sep 2010 by Richard Kimber Post: How may I ensure that I only run one work unit at a time? Recently I have been getting two that, because of the long computation times, are both run at high priority, thus excluding work on other projects.