Posts by Bernard 64250

1) Message boards : Questions and problems : Multiple Projects (Message 45460)
Posted 26 Aug 2012 by Bernard 64250
Post:
This is the theory, but the facts are different.

I have 2 Core 2 Duo computers running Boinc 7.0.31. The minimum reserve of work is set to 3 days with a threshold of 0.01 day.
They are connected to 3 projects that should equally share the CPU resources (100 / 100 / 100). According to a simple calculation (3 days x 2 cores / 3 projects), they should maintain a minimum workload of 48 hours.

But it doesn't work this way.
On both computers:
- 1 project has 1 WU active with more then 200 hours of work to do and a very long deadline. That sounds normal.
- 1 project has no pending work, with message "Not requesting tasks: don't need".
- 1 project has a lot of WUs in queue (22 WUs for a total workload of 140 hours on one computer, 13 WUs for a total workload of 152 hours on the other). By chance, the deadlines are long enough to let computing time to the other projects.
Before, my computers were attached to a project with short deadlines, and its WUs were always running in high priority, so a single project was using 100% of the resources when 3 projects should share them.
2) Message boards : Questions and problems : Good Projects for Older CPU's (Message 45133)
Posted 1 Aug 2012 by Bernard 64250
Post:
It is not easy to find WUs lasting for less than 12 hours on a Core 2 Duo à 2.53.

I run such projects on 2 "old" computers witk Core 2 Duo :
- Docking@home (not running under OSX).
- Enigma (no work available).
3) Message boards : Questions and problems : BOINC not getting tasks, despite being below the low-water mark (Message 44656)
Posted 28 Jun 2012 by Bernard 64250
Post:
There is a description of the bug in FAQ: BOINC 7.0.

The best thing to do is to let things go without any manual intervention.
4) Message boards : Questions and problems : I've a lot of problems with the 7.0 task scheduler. (Message 44655)
Posted 28 Jun 2012 by Bernard 64250
Post:
Don't loose time. I've found a description of the bug in FAQ: BOINC 7.0.
5) Message boards : Questions and problems : I've a lot of problems with the 7.0 task scheduler. (Message 44635)
Posted 27 Jun 2012 by Bernard 64250
Post:
2 days ago, I changed my cache settings to 4 and 0.01.

So I've got :
- 400 hours of workload for 1 project and 0 for the others on Quad Core computers.
- 200 hours of workload for 1 project and 0 for the others on Dual Core computers.

In all cases, it corresponds to 4 days * number of cores.

If their deadline is short, WUs are working in high priority. Please note that I've inherited of several pre-existing WUs when I switched to 7.0.

This may be a transient situation and I need to wait for a few days without any manual intervention to see how it evoluates.
6) Message boards : Questions and problems : BOINC not getting tasks, despite being below the low-water mark (Message 44628)
Posted 26 Jun 2012 by Bernard 64250
Post:
I'm progressing.

Each computer seems to have a "lucky project" which receives workload for all computer's cores. With my current settings (4 days + 0.1 day, 4 or 5 projects running with equal priority - 100), the workload for this project is always superior to 96h * number of cores (192 hours for a dual core, 384 hours for a quad core).
Please note that all my computers haven't the same "lucky" project.

Then 2 situations :
- if the WU deadline is short, tasks will run in high priority and the other projects will never receive new WUs. That's what happens to one of my computers.
- if the WU deadline is long enough, there is some time free for the other projects. They receive 1 WU at a time on a round robin mode, and it may take a very long time before getting automatic updates and new WUs for all projects. That's what happens to my other 2 computers.

I would like to suggest a SW modification.
7) Message boards : Questions and problems : BOINC not getting tasks, despite being below the low-water mark (Message 44627)
Posted 25 Jun 2012 by Bernard 64250
Post:
I don't know what was planned, but it's clear that these figures don't apply individually to each project : for the time being, on my 3 computers running 7.0.28, only one project receives new WUs. Other projects have terminated crunching all WUs and uploaded the results, but are still waiting for WU completion.

I've changed the limits to 4 days + 0.1 day and I'll see what happens.
8) Message boards : Questions and problems : BOINC not getting tasks, despite being below the low-water mark (Message 44564)
Posted 20 Jun 2012 by Bernard 64250
Post:
It's true that 7.0.28 is better than 7.0.25. But there is still some progress to do.

I've switched 3 of my computers from 7.0.25 to 7.0.28 (1 Mac + 2 32-bit PCs). Each computer is connected to 4 or 5 projects with equal priority (100). The minimum workload is set to 2 days and the maximum workload to 3 days.

On all computers, the same active project (Einstein) has a large amount of work pending and seems to receive new WUs each time that 2 WUs complete. That sounds OK.

On 2 computers (out of 3 connected), another project (Climate Prediction) is running with one long WU (2 weeks). The 3rd computer has fully completed and reported its last WU and is desesperately waiting for a new one.

All other projects have 100% completed their pending WUs and are desesperately waiting for task completion and/or new WUs. For these projects, manual project updates can solve the lack of automatic requests, but then you have again to desesperately wait for new WUs. Project suspension and task abort may also give good results if forcing a request to the scheduler, but disconnect/reconnect seems to be the only secure way to get new WUs (with the risk of loosing WUs waiting for completion). And it works ! So these projects are not out of work.
9) Message boards : Questions and problems : I've a lot of problems with the 7.0 task scheduler. (Message 44544)
Posted 18 Jun 2012 by Bernard 64250
Post:
To TRuEQ & TuVaLu
No chance to read your thread. It has been hidden by moderators.
10) Message boards : Questions and problems : I've a lot of problems with the 7.0 task scheduler. (Message 44542)
Posted 18 Jun 2012 by Bernard 64250
Post:
My first post was just to see if other users have similar problems.

I'm running BOINC 7.0.25 on OSX (1 host) and Windows XP (2 hosts). No GPU used.

After a few days, the only projects running are those who initially receive a large provision of work (as Climate Prediction). The other projects have 100% completed their WUs and haven't got new ones.

- There is no automatic update even if all WUs 100% complete for a project. Finished WUs remain waiting for completion for days. Manual updates are necessary to clean the queue.
- There is no automatic download of new WUs for projects waiting for work. In case of manual update, there is no new WU required even if no more work to do. To get new WUs, it's necessary to detach from the project and reattach.
- The WUs received don't respect the user-defined preferences (home/school/work) in term of applications. Non-selected applications are received even if not allowed.
- The new WUs received don't start automatically (according to time sharing). To start them, it's necessary to manually suspend the other projects.
- With multicore processors running 2 projects with equal priority, you may have all cores working on the same project for 1 hour then all cores switching to the other project, and so on, but never 50-50.

Reloading the BOINC application doesn't change anything. The only effect is the risk of loosing 100% completed WUs waiting fot completion.

I recently switched to 7.0.28 that seems to have a slightly better behaviour, especially fot Multicore processors, but the other problems remain.
11) Message boards : Questions and problems : I've a lot of problems with the 7.0 task scheduler. (Message 44083)
Posted 10 May 2012 by Bernard 64250
Post:
I've a lot of problems with the 7.0 task scheduler.




Copyright © 2022 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.