project is not highest priority...
This is not making sense.

I have like 3 Moowrap tasks in cue and 1 is running. Needs alot more to fill some of the cue of 1 day set.
Seti ati ap has 2 tasks running. 0 tasks in cue of 1 day cue.

It doesn't fill up the cache of either project. I run theese 2 GPU projects.
Or even tries.

It seems though it asks for new tasks sometimes when the last task in cue is running.

Why is this?

part of messages log....

-----------

2013-02-22 20:12:04 | SETI@home | Computation for task ap_27jl12ad_B2_P1_00120_20130222_29380.wu_1 finished
2013-02-22 20:12:04 | SETI@home | Starting task ap_18se12ab_B5_P1_00227_20130221_12826.wu_2 using astropulse_v6 version 604 (ati_opencl_100) in slot 6
2013-02-22 20:12:06 | SETI@home | Started upload of ap_27jl12ad_B2_P1_00120_20130222_29380.wu_1_0
2013-02-22 20:12:11 | SETI@home | Finished upload of ap_27jl12ad_B2_P1_00120_20130222_29380.wu_1_0
2013-02-22 20:12:11 | SETI@home | Sending scheduler request: To report completed tasks.
2013-02-22 20:12:11 | SETI@home | Reporting 1 completed tasks
2013-02-22 20:12:11 | SETI@home | Not requesting tasks: project is not highest priority
2013-02-22 20:12:17 | MindModeling@Beta | Computation for task MindModeling-363-5127a38e8f1b1_0 finished
2013-02-22 20:12:17 | MindModeling@Beta | Starting task MindModeling-364-5127a36ceeeac_0 using python2.7_wrap version 102 (sse2) in slot 4
2013-02-22 20:12:23 | MindModeling@Beta | Started upload of MindModeling-363-5127a38e8f1b1_0_0
2013-02-22 20:12:23 | SETI@home | Scheduler request completed
2013-02-22 20:12:27 | MindModeling@Beta | Finished upload of MindModeling-363-5127a38e8f1b1_0_0
2013-02-22 20:12:28 | MindModeling@Beta | Sending scheduler request: To report completed tasks.
2013-02-22 20:12:28 | MindModeling@Beta | Reporting 1 completed tasks
2013-02-22 20:12:28 | MindModeling@Beta | Requesting new tasks for CPU
2013-02-22 20:12:31 | MindModeling@Beta | Scheduler request completed: got 1 new tasks
2013-02-22 20:12:33 | MindModeling@Beta | Started download of MindModeling-365-5127c24c824bc_input
2013-02-22 20:12:35 | MindModeling@Beta | Finished download of MindModeling-365-5127c24c824bc_input
2013-02-22 20:12:41 | MindModeling@Beta | Sending scheduler request: To fetch work.
2013-02-22 20:12:41 | MindModeling@Beta | Requesting new tasks for CPU
2013-02-22 20:12:43 | MindModeling@Beta | Scheduler request completed: got 0 new tasks
2013-02-22 20:12:43 | MindModeling@Beta | No tasks sent
2013-02-22 20:12:43 | MindModeling@Beta | This computer has reached a limit on tasks in progress

As I suspected when the last moowrapper task was started the BM requested new work for Moo. I got 170 of them and they have an aprox runtime of 11-20 minutes depending on the amount of Seti ap's I get.

So no I end up with alot of Moowrapper tasks.
And when Seti does not ask very often and somtimes has or have tasks to send....

It's ok.

It's the same thing as when BM 7.x.x was developed.
It hasn't changed.
I was naive to think that had changed with BM .42+

BM .28 worked beter then .52

I got me more "equal flow"(stabile) in the downloads and requests with .28.

I got me 1 Seti ap tasks as well.

No seti tasks in cue...

2013-02-24 18:55:44 | SETI@home | update requested by user
2013-02-24 18:55:48 | SETI@home | Sending scheduler request: Requested by user.
2013-02-24 18:55:48 | SETI@home | Reporting 1 completed tasks
2013-02-24 18:55:48 | SETI@home | Not requesting tasks: project is not highest priority
2013-02-24 18:56:09 | SETI@home | Scheduler request failed: Couldn't connect to server

It is tough trying to get seti ap's nowadays.

Do you read your own logs? What do you think that Scheduler request failed: Couldn't connect to server means? Have you not noticed that Seti has had an expected power outage for 2 days, and that they have only just been back and thus that it will take several hours if not days before things go status quo there?

Restarting a project's servers isn't akin to restarting your PC. other than that you do so on both by pressing a power button, all similarities are out.

As for the message of the project not being the highest priority, this is the highest priority in work fetch. One of the other project will have a higher priority for work fetch, you can see which one that is when you enable the <work_fetch_debug/> flag in cc_config.xml

BOINC 7.0 will only fetch work from different projects when you set separately that the CPU should work only on project A and the GPU only on project B. It will no longer fetch work for all allowed projects, or at least that's how I understand that the changes have been. It'll run the projects one after another, and fetch work only for the project that has the highest fetch priority according to same average of work done on the same hardware resource.

English lesson: It isn't cue, it's queue. A cue is the stick that you play billiards and snooker with. A queue, although pronounced the same, is a row of things, like cars waiting for an accident to clear, or in this case tasks waiting to run. It's not que either, as that's Spanish for "what?"

---

Same as before:

http://boinc.berkeley.edu/dev/forum_thread.php?id=8196&postid=47823

Learn to read your own logs. Here's a single work fetch cycle from lower down, and its outcome:

2013-02-17 08:45:38 | | [work_fetch] work fetch start
2013-02-17 08:45:38 | | [work_fetch] ATI: buffer_low: yes; sim_excluded_instances 0
2013-02-17 08:45:38 | | [work_fetch] set_request(): ninst 3 nused_total 1.000000 nidle_now 0.000000 fetch share 1.000000 req_inst 0.000000
2013-02-17 08:45:38 | | [work_fetch] ------- start work fetch state -------
2013-02-17 08:45:38 | | [work_fetch] target work buffer: 259200.00 + 43200.00 sec
2013-02-17 08:45:38 | | [work_fetch] --- project states ---
2013-02-17 08:45:38 | Moo! Wrapper | [work_fetch] REC 69099.529 prio -1.000982 can req work
2013-02-17 08:45:38 | OProject@Home | [work_fetch] REC 82.896 prio -0.000236 can't req work: scheduler RPC backoff (backoff: 515.56 sec)
2013-02-17 08:45:38 | SETI@home | [work_fetch] REC 59664.099 prio -0.778463 can't req work: scheduler RPC backoff (backoff: 45.02 sec)
2013-02-17 08:45:38 | SETI@home Beta Test | [work_fetch] REC 46196.671 prio -4.096825 can't req work: "no new tasks" requested via Manager
2013-02-17 08:45:38 | WUProp@Home | [work_fetch] REC 0.002 prio -0.000009 can't req work: non CPU intensive
2013-02-17 08:45:38 | FreeHAL@home | [work_fetch] REC 0.020 prio 0.000000 can't req work: non CPU intensive
2013-02-17 08:45:38 | | [work_fetch] --- state for CPU ---
2013-02-17 08:45:38 | | [work_fetch] shortfall 1209096.29 nidle 3.00 saturated 0.00 busy 0.00
2013-02-17 08:45:38 | Moo! Wrapper | [work_fetch] fetch share 0.000 (blocked by prefs) (no apps)
2013-02-17 08:45:38 | OProject@Home | [work_fetch] fetch share 0.000
2013-02-17 08:45:38 | SETI@home | [work_fetch] fetch share 0.000 (blocked by prefs) (no apps)
2013-02-17 08:45:38 | SETI@home Beta Test | [work_fetch] fetch share 0.000 (blocked by prefs)
2013-02-17 08:45:38 | | [work_fetch] --- state for ATI ---
2013-02-17 08:45:38 | | [work_fetch] shortfall 842913.07 nidle 0.00 saturated 6016.78 busy 0.00
2013-02-17 08:45:38 | Moo! Wrapper | [work_fetch] fetch share 1.000
2013-02-17 08:45:38 | OProject@Home | [work_fetch] fetch share 0.000 (no apps)
2013-02-17 08:45:38 | SETI@home | [work_fetch] fetch share 0.000
2013-02-17 08:45:38 | SETI@home Beta Test | [work_fetch] fetch share 0.000
2013-02-17 08:45:38 | | [work_fetch] ------- end work fetch state -------
2013-02-17 08:45:38 | Moo! Wrapper | [sched_op] Starting scheduler request
2013-02-17 08:45:38 | Moo! Wrapper | [work_fetch] request: CPU (0.00 sec, 0.00 inst) ATI (842913.07 sec, 0.00 inst)
2013-02-17 08:45:38 | Moo! Wrapper | Sending scheduler request: To report completed tasks.
2013-02-17 08:45:38 | Moo! Wrapper | Reporting 1 completed tasks
2013-02-17 08:45:38 | Moo! Wrapper | Requesting new tasks for ATI
2013-02-17 08:45:38 | Moo! Wrapper | [sched_op] CPU work request: 0.00 seconds; 0.00 devices
2013-02-17 08:45:38 | Moo! Wrapper | [sched_op] ATI work request: 842913.07 seconds; 0.00 devices
2013-02-17 08:45:43 | Moo! Wrapper | Scheduler request completed: got 10 new tasks

At that time, OProject had the highest priority (note that all numbers are negative): SETI@home had middle priority: and Moo! Wrapper had lowest priority.

Both OP and SETI were being delayed before attempting to pester their servers again ('RPC backoff' - Remote Procedure Call). Moo was fetchable - work was requested and allocated. That's how it works.

If you try to bypass normal scheduling by clicking the update button, BOINC will only request work from the highest priority project. We have had bugs with that: it should be the highest priority fetchable project, and I think it's fixed now in v7.0.52. You would have to match up the work fetch cycle in the log with the time you clicked the button. Please do that in the peace and comfort of your own home: we don't need a new log snippet for every twist and turn in your search

Moo Wrapper, Seti and Seti Beta have done too much work for your resource share, other projects need to do work to bring your those project priorities back towards zero,
with your 3 GPUs configured to run on single projects each that is unlikely to ever happen,

2013-02-17 08:29:55 | Moo! Wrapper | Config: excluded GPU. Type: all. App: all. Device: 0
2013-02-17 08:29:55 | Moo! Wrapper | Config: excluded GPU. Type: all. App: all. Device: 2
2013-02-17 08:29:55 | SETI@home Beta Test | Config: excluded GPU. Type: all. App: all. Device: 1
2013-02-17 08:29:55 | SETI@home | Config: excluded GPU. Type: all. App: all. Device: 1
2013-02-17 08:29:55 | Moo! Wrapper | URL http://moowrap.net/; Computer ID 15827; resource share 80
2013-02-17 08:29:55 | OProject@Home | URL http://oproject.info/; Computer ID 565; resource share 400
2013-02-17 08:29:55 | SETI@home | URL http://setiathome.berkeley.edu/; Computer ID 6910524; resource share 100
2013-02-17 08:29:55 | SETI@home Beta Test | URL http://setiweb.ssl.berkeley.edu/beta/; Computer ID 62304; resource share 20
2013-02-17 08:29:55 | WUProp@Home | URL http://wuprop.boinc-af.org/; Computer ID 48671; resource share 100
2013-02-17 08:29:55 | FreeHAL@home | URL http://www.freehal.net/freehal_at_home/; Computer ID 85349; resource share 100

Claggy

Do you read your own logs? What do you think that Scheduler request failed: Couldn't connect to server means? Have you not noticed that Seti has had an expected power outage for 2 days, and that they have only just been back and thus that it will take several hours if not days before things go status quo there?

Restarting a project's servers isn't akin to restarting your PC. other than that you do so on both by pressing a power button, all similarities are out.

As for the message of the project not being the highest priority, this is the highest priority in work fetch. One of the other project will have a higher priority for work fetch, you can see which one that is when you enable the <work_fetch_debug/> flag in cc_config.xml

BOINC 7.0 will only fetch work from different projects when you set separately that the CPU should work only on project A and the GPU only on project B. It will no longer fetch work for all allowed projects, or at least that's how I understand that the changes have been. It'll run the projects one after another, and fetch work only for the project that has the highest fetch priority according to same average of work done on the same hardware resource.

English lesson: It isn't cue, it's queue. A cue is the stick that you play billiards and snooker with. A queue, although pronounced the same, is a row of things, like cars waiting for an accident to clear, or in this case tasks waiting to run. It's not que either, as that's Spanish for "what?"

Hi.

Thank you for your English lesson.
I always forgot that cue was the pin for pool playing.

I solved my problem today after writing the last post.
I uninstalled .52 and reinstalled .28
Now is the problem getting workunits of type astropulse to my little PC which is built of used parts only. I can't afford new high tech piece of equipment since I am not a very rich guy.

Somehow Seti will find a way to supply wu's to us in Northern Europe....
Is it us as in US or....
In my language oss or OSS is the same meaning as us or US.

But no language lesson needed here I hope.
That was just for fun.

Thank you Claggy

I just consider it to not work properly when I am out of Wu's and BM doesn't request work.

I still run 98% Moowrapper tasks.
I run all the ap's I get if I get any.

I just consider it to not work properly when I am out of Wu's and BM doesn't request work.

Boinc Manager is the GUI (the Graphical User Interface), it doesn't request work and never will, that is the Boinc client's job.

Claggy

BM .56 asks for work in a more aggressive way.
Looks promising.

AGELESS,

Thank you for your explanation of how the priority works for fetching work. Yours was the clearest explanation I have seen. One comment I would like to make is your correction of the other persons spelling and grammar. We have people all over the globe working on Boinc projects. I would hope that the people working on SETI would be the least Xenophobic of all BOINC volunteers. Besides doing work on SETI, I volunteer work on medical research. These project are for researchers all over the globe. English is the first language for only a portion of the volunteers processing work for SETI and other BOINC projects.

How is your spelling in other languages other than English? Could you have answered his question in Swedish? Both queue and cue are kö in Swedish, and both English words come from the same French root word cue. If we do someday get evidence of EM transmission from beings elsewhere in the universe, do you expect them to speak English?

Greg

I'm an American and am sometimes ashamed of it.

A person who speaks more than one languages is called multilingual.

People who speak only one language are called Americans.

People who are proud of their limited language skills are ignorant.