Hey everyone,

There was a problem with the previous separation runs that was causing some command lines to overflow. I have changed the bundle size of the new runs, so that shouldn't be a problem anymore. The previous runs have been taken down.

The names of the new runs are:

de_modfit_80_bundle4_4s_south4s_0
de_modfit_81_bundle4_4s_south4s_0
de_modfit_82_bundle4_4s_south4s_0
de_modfit_83_bundle4_4s_south4s_0
de_modfit_84_bundle4_4s_south4s_0
de_modfit_85_bundle4_4s_south4s_0
de_modfit_86_bundle4_4s_south4s_0

These new workunits will crunch a little faster than the previous versions, and credits are assigned accordingly.

Thank you all for your patience during this transition period!

Tom

hi, i run my radeon vii 24hours, i noticed in between WU's downloaded from servers, it took 12minutes in between WU's download, not acceptable, if i manually click "update" it downloads new WU's in less then 1minute, im not around 24hours , my 6850k idles at 190watts , it costs me approximately 40centsAUD per Kilowatt here , don't make me change projects because i don't want to , FIX ASAP please , you guys are on a salary im not

---

hi, i run my radeon vii 24hours, i noticed in between WU's downloaded from servers, it took 12minutes in between WU's download, not acceptable, if i manually click "update" it downloads new WU's in less then 1minute, im not around 24hours , my 6850k idles at 190watts , it costs me approximately 40centsAUD per Kilowatt here , don't make me change projects because i don't want to , FIX ASAP please , you guys are on a salary im not

Two thing....1st is don't be such a dick. Most them are volunteers not getting paid either. 2nd is use the search function and you could habe seen whats going on easily...

https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=4424

https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=4434

Your welcome and good day!

https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=4424

Is downgrading to BOINC 7.12 a successful solution then?

Guess I'll try it just in case.

yeah well im not going to downgrade my time either, im not into marketing, fix it ,

---

Hello Hurr1cane,

This problem has been discussed in greater detail here: https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=4434
It's an issue with the BOINC client as far as we know, what happens is that your computer won't automatically download more WU's until your job queue is complete, which can sometimes include validation of previous WU's. Sorry for the inconvenience, and know that we're looking into a solution for the future.

These runs have converged and have been taken down.

Until more separation runs are put up, your machine will only pull N-body workunits from the server (you may still get some separation WUs over the next few days as validations trickle in and your queues clear out). I know some people have turned off receiving workunits from N-body on their machine, which means that you might not pull workunits from milkyway unless that setting is changed. If this is a problem I can always put up some new separation runs in the meantime while we analyze the results from these runs.

Thank you all for your help and continued support,

- Tom

At the moment i wasn't able to download workunits in none of my hosts
sometimes i'm able to download 2-6workunits but but mostly 0

273030 Milkyway@Home 31/05/2019 09:00:03 Requesting new tasks for AMD/ATI GPU
273031 Milkyway@Home 31/05/2019 09:00:05 Scheduler request completed: got 0 new tasks
273032 Milkyway@Home 31/05/2019 09:04:57 update requested by user
273033 Milkyway@Home 31/05/2019 09:04:59 Sending scheduler request: Requested by user.
273034 Milkyway@Home 31/05/2019 09:04:59 Requesting new tasks for AMD/ATI GPU
273035 Milkyway@Home 31/05/2019 09:05:00 Scheduler request completed: got 0 new tasks
273036 Milkyway@Home 31/05/2019 09:06:32 Sending scheduler request: To fetch work.
273037 Milkyway@Home 31/05/2019 09:06:32 Requesting new tasks for AMD/ATI GPU
273038 Milkyway@Home 31/05/2019 09:06:33 Scheduler request completed: got 0 new tasks
273039 Milkyway@Home 31/05/2019 09:17:01 update requested by user
273040 Milkyway@Home 31/05/2019 09:17:01 Sending scheduler request: Requested by user.
273041 Milkyway@Home 31/05/2019 09:17:01 Requesting new tasks for AMD/ATI GPU
273042 Milkyway@Home 31/05/2019 09:17:02 Scheduler request completed: got 0 new tasks
273043 Milkyway@Home 31/05/2019 09:18:34 Sending scheduler request: To fetch work.
273044 Milkyway@Home 31/05/2019 09:18:34 Requesting new tasks for AMD/ATI GPU
273045 Milkyway@Home 31/05/2019 09:18:35 Scheduler request completed: got 0 new tasks

Automated requests gave the same results and queue is empty an all hosts

---

Want your Kids stay off from Drugs? Get them building Crunching PC's and they'll never have enough money for drugs

Hello Hurr1cane,

This problem has been discussed in greater detail here: https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=4434
It's an issue with the BOINC client as far as we know, what happens is that your computer won't automatically download more WU's until your job queue is complete, which can sometimes include validation of previous WU's. Sorry for the inconvenience, and know that we're looking into a solution for the future.

So you are saying that the problem is your software can't differentiate between batches of wu's so it can't download multiple batches of wu's? That seems silly and a programming problem.

Thanks but this is something different..

the queue is empty since yesterday evening.. usually i can download about 2-300 wu per gpu (only when queue is empty as the issue you explained) but since this night the queue is completely empty and i always have the message "Scheduler request completed: got 0 new tasks " exept sometimes when downloads 2-10 workunits per host..

---

Want your Kids stay off from Drugs? Get them building Crunching PC's and they'll never have enough money for drugs

This problem has been discussed in greater detail here: https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=4434
It's an issue with the BOINC client as far as we know, what happens is that your computer won't automatically download more WU's until your job queue is complete, which can sometimes include validation of previous WU's. Sorry for the inconvenience, and know that we're looking into a solution for the future.

It would be nice if the Event Log could say something other than the queue is full (when it is not full). I find it frustrating to tweak for this project and be denied work units because I am successful running sixteen WUs simultaneously on two AMD HD 7990s.

It would be nice if the Event Log could say something other than the queue is full (when it is not full). I find it frustrating to tweak for this project and be denied work units because I am successful running sixteen WUs simultaneously on two AMD HD 7990s.

It can, you just need to add debug lines to your cc_config file. Try adding <sched_op_debug> and <work_fetch_debug>. Post results here and someone that is more knowledgeable than me will be able to help solve it.

(edited for typos)

At the moment i wasn't able to download workunits in none of my hosts
sometimes i'm able to download 2-6workunits but but mostly 0

273030 Milkyway@Home 31/05/2019 09:00:03 Requesting new tasks for AMD/ATI GPU
273031 Milkyway@Home 31/05/2019 09:00:05 Scheduler request completed: got 0 new tasks
273032 Milkyway@Home 31/05/2019 09:04:57 update requested by user
273033 Milkyway@Home 31/05/2019 09:04:59 Sending scheduler request: Requested by user.
273034 Milkyway@Home 31/05/2019 09:04:59 Requesting new tasks for AMD/ATI GPU
273035 Milkyway@Home 31/05/2019 09:05:00 Scheduler request completed: got 0 new tasks
273036 Milkyway@Home 31/05/2019 09:06:32 Sending scheduler request: To fetch work.
273037 Milkyway@Home 31/05/2019 09:06:32 Requesting new tasks for AMD/ATI GPU
273038 Milkyway@Home 31/05/2019 09:06:33 Scheduler request completed: got 0 new tasks
273039 Milkyway@Home 31/05/2019 09:17:01 update requested by user
273040 Milkyway@Home 31/05/2019 09:17:01 Sending scheduler request: Requested by user.
273041 Milkyway@Home 31/05/2019 09:17:01 Requesting new tasks for AMD/ATI GPU
273042 Milkyway@Home 31/05/2019 09:17:02 Scheduler request completed: got 0 new tasks
273043 Milkyway@Home 31/05/2019 09:18:34 Sending scheduler request: To fetch work.
273044 Milkyway@Home 31/05/2019 09:18:34 Requesting new tasks for AMD/ATI GPU
273045 Milkyway@Home 31/05/2019 09:18:35 Scheduler request completed: got 0 new tasks

Automated requests gave the same results and queue is empty an all hosts

There is no GPU version of N-body implemented yet. If you are not running CPU I believe you won't be able to pull tasks for the moment.

I will put up some new separation runs later so that we don't waste GPU cycles.

- Tom

With new gpu runs everything is looking fine and as usual

Looking at statistics the problem was general and i wasn't the only, almost everyone had this drop

But with new wu seems to be ok

---

Want your Kids stay off from Drugs? Get them building Crunching PC's and they'll never have enough money for drugs

https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=4424

Is downgrading to BOINC 7.12 a successful solution then?

Guess I'll try it just in case.

I believe the true solution would be to upgrade to the latest 7.15.0 master which has an improved work fetch to prevent idle cores, fetching work when work is returned and not requesting work over excessive scheduler backoff intervals.

But you need to compile the master yourself or get the latest appveyor client artifact and try running that. You can download the Windows client appveyor artifact here.
https://ci.appveyor.com/api/buildjobs/4qe96bvaqh4cklou/artifacts/deploy%2Fwin-client%2Fwin-client_PR3169_2019-05-29_4928cc96.7z

I run Linux so can't make any valid statement about how Windows behaves, but the work fetch has been significantly improved since the release of the official 7.14.2 client.

I don't have any issues getting MilkyWay work, or work from any project for that matter and maintaining my cache levels. As long as work is to be found, I get it when I request it. Setting the sched_ops flag and/or also the work_fetch_debug flag logging options for the Event Log will show how much work is requested at each scheduler connection and also the shortfall on each project and how busy BOINC thinks your client is among all attached projects. Those logging options point out very well why a client does not request work.

---

I believe the true solution would be to upgrade to the latest 7.15.0 master which has an improved work fetch to prevent idle cores, fetching work when work is returned and not requesting work over excessive scheduler backoff intervals.

How long before you release 7.15 for testing to the test group? I haven't seen it there yet so am guessing you are still working on it, or I missed it.

I believe the true solution would be to upgrade to the latest 7.15.0 master which has an improved work fetch to prevent idle cores, fetching work when work is returned and not requesting work over excessive scheduler backoff intervals.

How long before you release 7.15 for testing to the test group? I haven't seen it there yet so am guessing you are still working on it, or I missed it.

I don't know. I'm not privy to the information. All I can say is to watch the Milestone tab for 7.16.0. They don't set any calendar date for release. They just make a group decision whether a client is ready for release. I think DA is the final arbiter of when to release but he gets input from all the project administrators and developers.
The 7.16.0 milestone progress is here. https://github.com/BOINC/boinc/projects/14
Says 10 done, 3 in progress.

---

I believe the true solution would be to upgrade to the latest 7.15.0 master which has an improved work fetch to prevent idle cores, fetching work when work is returned and not requesting work over excessive scheduler backoff intervals.

How long before you release 7.15 for testing to the test group? I haven't seen it there yet so am guessing you are still working on it, or I missed it.

I don't know. I'm not privy to the information. All I can say is to watch the Milestone tab for 7.16.0. They don't set any calendar date for release. They just make a group decision whether a client is ready for release. I think DA is the final arbiter of when to release but he gets input from all the project administrators and developers.
The 7.16.0 milestone progress is here. https://github.com/BOINC/boinc/projects/14
Says 10 done, 3 in progress.

Thank you.

My best hunch is that there won't be a 7.16.0 release. The BOINC 8.0 Manager/Client milestone looks just as developed with more commits going into it than the 7.16.0 milestone. No expected date on it either. I think the 7.16.0 is actually going to be released as 8.0 as a hunch. But that is just my musings and guesses.

---

My best hunch is that there won't be a 7.16.0 release. The BOINC 8.0 Manager/Client milestone looks just as developed with more commits going into it than the 7.16.0 milestone. No expected date on it either. I think the 7.16.0 is actually going to be released as 8.0 as a hunch. But that is just my musings and guesses.

That might be cool!!