Boinc has always run in FIFO within a project. It only check due dates to prioritize work if there is a chance it won't be completed on time following the normal order.

Well, I have noticed that it is not working in FIFO basis. I had a lot of wu's -just one project, no mix- started but not completed, in waiting to run state. My wu's are usualy sorted by Report deadline and only this version jumps forth and backwards
I had several hours of work in a lot of "waiting to run" tasks, then decided to use 6.10.17 in all linux machines and I guess 6.10.18 to a pair of microsoft ones.

I think you may have misunderstood. By FIFO, I mean the order in which Boinc received the WU. This has always been the case. Boinc only uses the date and time it received a WU to determine which WU to run next, unless it needs to switch to high priority mode. It doesn't and never has cared how you sort the WU's. For some projects different WU can have different due dates. At Seti for example, depending on the amount of work expected on a work unit, due dates assigned can vary between 1 and 6 weeks.

I think you may have misunderstood. By FIFO, I mean the order in which Boinc received the WU.

I have learnt that in digital electronics long ago.
I have just reinstalled 6.10.56 in a quad machine and I can assure you that it didn't follow the order the tasks were received. It jumped more than 30 tasks and ignored the oldest ones(fifo ok by 6.10.17) that were already more than 30% done, and are now in waiting to run status.
But I will check it better...
Tks anyway.

I have seen this happening after two different type of events.

1- Boinc is now "Suspending computation - CPU usage is too high" and
2- Scheduled update of project with a switch to high priority mode.

If event 1 occurs frequently, as BOINC loads new wus, a lot of them are in waiting to run status. Solution: "Suspend work if non-BOINC load exceeds 0%"
I dont remember of so frequent changes of priority mode before, no idea yet...
Tks

Just to summarize, when upgraded from 61017 to 61056, many tasks were started but left incomplete to waiting to run status.
Then, after a reset to the Ibercivis project, new tasks have been received and everything was (FIFO) working perfectly.
Some hours later, attached to EDGeS project. The problem started again and worse is that several Ibercivis sanidad processes (60MiB+ per processs) and EDGeS fusion processes (400MiB+ per processs) were sleeping but occupying system resources. A quad desktop had 4 running EDGeS processes, 4 sleeping EDGeS processes plus 4 sleeping Ibercivis processes - sleeping processes occupying about 2GiB memory.
Resource share doesn't work but it works with the combination of Ibercivis and ABC projects.
It would be nice to totally separate prefs, no general prefs from one project to all, just to manage projects individually. Is it possible?
Back to 61017 and no problems.
(Sanidad tasks, 10 minutes each and EDGeS tasks, 10 to 40 minutes each.)
Tks.

On WINDOWS remote desktop access GPU tasks are stopped and fail to continue after leaving the RDP session.

http://www.xtremesystems.org/forums/showpost.php?s=c388c0d641058907115ba32bae58a20d&p=4297485&postcount=8

What's going on with the BOINK project?
No work, can't report completed files.
Running 6.10.56
My server is doing nothing but spinning my electric meter!

---

What's going on with the BOINK project?

There is no BOINC project. BOINC is the managing program for other (scientific) projects. So which project do you mean? If Seti, then look at their own web site.

---

On WINDOWS remote desktop access GPU tasks are stopped and fail to continue after leaving the RDP session.

As far as I read that thread, it's Windows 7 that has the problem. Which isn't that weird, as it's all new territory. I'll forward that to the developers.

---

sleeping processes occupying about 2GiB memory.

Don't use "Leave applications in memory while suspended".

---

On WINDOWS remote desktop access GPU tasks are stopped and fail to continue after leaving the RDP session.

As far as I read that thread, it's Windows 7 that has the problem. Which isn't that weird, as it's all new territory. I'll forward that to the developers.

I could just reproduce the same issue on a XP machine.
After leaving the remote session all tasks fail.
Tested with xp prof 32 sp3, ati hd2400, latest vga driver, project collatz.

After "real" login on host machine, tasks are processed normaly again.

Nice!

I downloaded subj release and shortly afterward I found 3 new client applications which appear to be using my computer without my authorization. I attempted to remove them but they kept re-installing. NIH/NIS, New York University/Wash State and one other. What is their purpose?
Also I am experiencing 30-50% PV's daily. Why such a high percentage?

I am not a techie, just your everyday garden variety PC user. Any info/assista
nce would be appreciated. Thank you. Bud

NIH/NIS, New York University/Wash State and one other. What is their purpose?

Which project or projects are you attached to?
On which operating system?

Also I am experiencing 30-50% PV's daily. Why such a high percentage?

What are PV's? For a non-techie you type in mysterious acronyms. :)

---

NIH/NIS, New York University/Wash State and one other. What is their purpose?

Which project or projects are you attached to?
On which operating system?

New York University/University of Washington sounds like HPF2 from WCG.

Also I am experiencing 30-50% PV's daily. Why such a high percentage?

What are PV's? For a non-techie you type in mysterious acronyms. :)

Most likely Pending Validation.

New York University/University of Washington sounds like HPF2 from WCG.

Yes, that's what I thought as well. So Bud check that you're attached to World Community Grid and whether it's allowed to fetch work or not.

What are PV's? For a non-techie you type in mysterious acronyms. :)

Most likely Pending Validation.[/quote]
If it's that, it's hardly a BOINC client problem. Pointing back to the project where Bud sees those.

---