There are several projects, carried out simultaneously:

Project / Application / Time for 1 WU / Pending WU's Time / Deadline time / Resource
--------------------------------------------------------------------------------------
MilkyWay / 1.02 MilkyWay@Home (opencl_amd_ati) / ~80sec / 51m36s / 11 days, 16h24m29s / 3000
POEM / 1.05 POEM++ OpenCL (opencl_ati_100) / ~40 min / 13h32m42s / 6 days, 2h44m10s / 3000
Einstein / 1.34 BRP Search (Arecibo) (opencl-ati) / ~18 min / 54m07s / 3 days, 2h15m00s / 100

As can see, no immediately deadline pending.

What is happened:

1) Starts MilkyWay application.
2) After 34 sec MilkyWay stops and starts POEM.
3) After ~10 min POEM stops and starts Einstein with HIGH PRIORITY.
4) After 3 min status of Einstein goes to Normal Priority.
5) Einstein complete, resumed POEM. Progress of POEM, of course, rolls back by 1-2.5 minutes (some work is wasted).
6) After 3..10 minutes POEM stops again and new Einstein is started again. Go to 3).
7) POEM is finally completed with 2-3 pauses. MilkyWay is resumed - it's progress also rolls back (62% -> 0%), and MilkyWay STARTS FROM BEGIN (!!!) again. Go to 1).
Some MilkyWay WU's began from the beginning several times... This simply enrages me... :(

I was observe the similar behavior earlier on BOINC 7.0.28 (not exact the same, but similar), on 7.0.42 yesterday and just now on 7.0.58.

There are some questions:
1) It is for which necessary to stop tasks with the short run time?
2) It is for which necessary to start tasks, if there are others with the deliberately high priority?
3) Making a decision about starting and pausing of applications actually cannot be put off to the moment of the completion of the already working application?
4) Is for which necessary this entire the super-high intellect of task manager, if it does interfere with the basic purpose of client - running the USEFUL application with minimal overhead?
As for me, a simple queue is better, than super-intellectual manager, which generates huge overhead and waste the already made work.

Similar theme about stopping application with near completion time began still in 2011, but instead of the solution of the problem this theme was declared not being subject to the consideration (See FAQ: Do not stop until it is over: at 98% or more, continue till end of task.).

Meanwhile the parameter 'Application switching interval' and the known expected time to the completion can be easily used for determining the need for the pausing of application.

My system: BOINC 7.x + Win7/x86; AMD Phenom X4 + AMD HD7950