is the old 6.45 better than the 6.6.36?

i keep piling up a huge load of rosie tasks and then ralph comes along and kicks in some work along with the existing einstein work and i soon have a rash of "high priority" tasks that are due in 3 days with ralph and rosie.

any ideas?

is the old 6.45 better than the 6.6.36?

i keep piling up a huge load of rosie tasks and then ralph comes along and kicks in some work along with the existing einstein work and i soon have a rash of "high priority" tasks that are due in 3 days with ralph and rosie.

any ideas?

The new 6.6.? versions have 'issues' with the long term debt when running multiple projects. It will run, in your case, einstein just fine but then all of a sudden stop einstein and only get units for ralph or rosie for a while. Now project deadlines are a whole other story and a different problem. No version of boinc does them any better than any other. When project a is cruising along with 5 day deadlines and then all of a sudden project b comes in with a 24 hour deadline, project b goes into the 'high priority' crunching mode and the other projects suffer as a result. THEN the ltd comes into play and project a should get all the crunching time for a bit, but with version 6.6.? there are 'issues'. So maybe they are related! The 'powers that be' are 'working' on the problem of the ltd scheduling in the 6.6.? versions.

Personally I have dropped back to 6.2.19 for all my machines except one that crunches for AQUA, that may stop here soon as the scheduling is funky, and one machine that runs Linux.

---

is the old 6.45 better than the 6.6.36?

i keep piling up a huge load of rosie tasks and then ralph comes along and kicks in some work along with the existing einstein work and i soon have a rash of "high priority" tasks that are due in 3 days with ralph and rosie.

any ideas?

The new 6.6.? versions have 'issues' with the long term debt when running multiple projects. It will run, in your case, einstein just fine but then all of a sudden stop einstein and only get units for ralph or rosie for a while. Now project deadlines are a whole other story and a different problem. No version of boinc does them any better than any other. When project a is cruising along with 5 day deadlines and then all of a sudden project b comes in with a 24 hour deadline, project b goes into the 'high priority' crunching mode and the other projects suffer as a result. THEN the ltd comes into play and project a should get all the crunching time for a bit, but with version 6.6.? there are 'issues'. So maybe they are related! The 'powers that be' are 'working' on the problem of the ltd scheduling in the 6.6.? versions.

Personally I have dropped back to 6.2.19 for all my machines except one that crunches for AQUA, that may stop here soon as the scheduling is funky, and one machine that runs Linux.

Thanks Mikey, I dropped back to 6.4.7 for Windows and I also noticed one other thing. My cpu temp droped 10 deg. F on both cores with the version change.
I am cranking a double Ralph at the moment, but earlier I was cranking ralph and rosie. The tempature signature on the cores is the same as earlier, just 10 degrees lower on the chart. Thats a very interesting discovery!

is the old 6.45 better than the 6.6.36?

i keep piling up a huge load of rosie tasks and then ralph comes along and kicks in some work along with the existing einstein work and i soon have a rash of "high priority" tasks that are due in 3 days with ralph and rosie.

any ideas?

The new 6.6.? versions have 'issues' with the long term debt when running multiple projects. It will run, in your case, einstein just fine but then all of a sudden stop einstein and only get units for ralph or rosie for a while. Now project deadlines are a whole other story and a different problem. No version of boinc does them any better than any other. When project a is cruising along with 5 day deadlines and then all of a sudden project b comes in with a 24 hour deadline, project b goes into the 'high priority' crunching mode and the other projects suffer as a result. THEN the ltd comes into play and project a should get all the crunching time for a bit, but with version 6.6.? there are 'issues'. So maybe they are related! The 'powers that be' are 'working' on the problem of the ltd scheduling in the 6.6.? versions.

Personally I have dropped back to 6.2.19 for all my machines except one that crunches for AQUA, that may stop here soon as the scheduling is funky, and one machine that runs Linux.

Thanks Mikey, I dropped back to 6.4.7 for Windows and I also noticed one other thing. My cpu temp droped 10 deg. F on both cores with the version change.
I am cranking a double Ralph at the moment, but earlier I was cranking ralph and rosie. The tempature signature on the cores is the same as earlier, just 10 degrees lower on the chart. Thats a very interesting discovery!

It is!! Are you still cranking units out in about the same time as before?

---

is the old 6.45 better than the 6.6.36?

i keep piling up a huge load of rosie tasks and then ralph comes along and kicks in some work along with the existing einstein work and i soon have a rash of "high priority" tasks that are due in 3 days with ralph and rosie.

any ideas?

The new 6.6.? versions have 'issues' with the long term debt when running multiple projects. It will run, in your case, einstein just fine but then all of a sudden stop einstein and only get units for ralph or rosie for a while. Now project deadlines are a whole other story and a different problem. No version of boinc does them any better than any other. When project a is cruising along with 5 day deadlines and then all of a sudden project b comes in with a 24 hour deadline, project b goes into the 'high priority' crunching mode and the other projects suffer as a result. THEN the ltd comes into play and project a should get all the crunching time for a bit, but with version 6.6.? there are 'issues'. So maybe they are related! The 'powers that be' are 'working' on the problem of the ltd scheduling in the 6.6.? versions.

Personally I have dropped back to 6.2.19 for all my machines except one that crunches for AQUA, that may stop here soon as the scheduling is funky, and one machine that runs Linux.

Thanks Mikey, I dropped back to 6.4.7 for Windows and I also noticed one other thing. My cpu temp droped 10 deg. F on both cores with the version change.
I am cranking a double Ralph at the moment, but earlier I was cranking ralph and rosie. The tempature signature on the cores is the same as earlier, just 10 degrees lower on the chart. Thats a very interesting discovery!

It is!! Are you still cranking units out in about the same time as before?

It seems that the scheduler works better as I got 13 new tasks in 12hrs one batch of 7 and one batch of 6. There are 4 tasks due to be completed still, so this is a more standard behavior that what 6.6.x was doing. My Ralph backlog is down to 1 and it ran Einstein for a bit to catch up the debt and now is back to high priority on 2 Rosie tasks that are due tomorow. Then I have a 5 day lead time on the next 4 in line. Seems that the scheduler is working better. Average cores temps run from 156-158 down from the upper 160's. So as I said, about a 10 deg. F drop. One core always runs a bit hotter than the other but it only spikes above 160 for a few seconds. I am using speedfan to monitor the core temps. Low temp on one core goes down about the 150 mark while the other stays pretty tight around the 158 mark. Still lower than before.

is the old 6.45 better than the 6.6.36?

i keep piling up a huge load of rosie tasks and then ralph comes along and kicks in some work along with the existing einstein work and i soon have a rash of "high priority" tasks that are due in 3 days with ralph and rosie.

any ideas?

The new 6.6.? versions have 'issues' with the long term debt when running multiple projects. It will run, in your case, einstein just fine but then all of a sudden stop einstein and only get units for ralph or rosie for a while. Now project deadlines are a whole other story and a different problem. No version of boinc does them any better than any other. When project a is cruising along with 5 day deadlines and then all of a sudden project b comes in with a 24 hour deadline, project b goes into the 'high priority' crunching mode and the other projects suffer as a result. THEN the ltd comes into play and project a should get all the crunching time for a bit, but with version 6.6.? there are 'issues'. So maybe they are related! The 'powers that be' are 'working' on the problem of the ltd scheduling in the 6.6.? versions.

Personally I have dropped back to 6.2.19 for all my machines except one that crunches for AQUA, that may stop here soon as the scheduling is funky, and one machine that runs Linux.

Thanks Mikey, I dropped back to 6.4.7 for Windows and I also noticed one other thing. My cpu temp droped 10 deg. F on both cores with the version change.
I am cranking a double Ralph at the moment, but earlier I was cranking ralph and rosie. The tempature signature on the cores is the same as earlier, just 10 degrees lower on the chart. Thats a very interesting discovery!

It is!! Are you still cranking units out in about the same time as before?

It seems that the scheduler works better as I got 13 new tasks in 12hrs one batch of 7 and one batch of 6. There are 4 tasks due to be completed still, so this is a more standard behavior that what 6.6.x was doing. My Ralph backlog is down to 1 and it ran Einstein for a bit to catch up the debt and now is back to high priority on 2 Rosie tasks that are due tomorow. Then I have a 5 day lead time on the next 4 in line. Seems that the scheduler is working better. Average cores temps run from 156-158 down from the upper 160's. So as I said, about a 10 deg. F drop. One core always runs a bit hotter than the other but it only spikes above 160 for a few seconds. I am using speedfan to monitor the core temps. Low temp on one core goes down about the 150 mark while the other stays pretty tight around the 158 mark. Still lower than before.

That sounds like it should be the new default for Boinc!! More units in the cache, scheduler is better, no slowdown in crunching AND it runs cooler on top of all that!

---

is the old 6.45 better than the 6.6.36?

i keep piling up a huge load of rosie tasks and then ralph comes along and kicks in some work along with the existing einstein work and i soon have a rash of "high priority" tasks that are due in 3 days with ralph and rosie.

any ideas?

The new 6.6.? versions have 'issues' with the long term debt when running multiple projects. It will run, in your case, einstein just fine but then all of a sudden stop einstein and only get units for ralph or rosie for a while. Now project deadlines are a whole other story and a different problem. No version of boinc does them any better than any other. When project a is cruising along with 5 day deadlines and then all of a sudden project b comes in with a 24 hour deadline, project b goes into the 'high priority' crunching mode and the other projects suffer as a result. THEN the ltd comes into play and project a should get all the crunching time for a bit, but with version 6.6.? there are 'issues'. So maybe they are related! The 'powers that be' are 'working' on the problem of the ltd scheduling in the 6.6.? versions.

Personally I have dropped back to 6.2.19 for all my machines except one that crunches for AQUA, that may stop here soon as the scheduling is funky, and one machine that runs Linux.

Thanks Mikey, I dropped back to 6.4.7 for Windows and I also noticed one other thing. My cpu temp droped 10 deg. F on both cores with the version change.
I am cranking a double Ralph at the moment, but earlier I was cranking ralph and rosie. The tempature signature on the cores is the same as earlier, just 10 degrees lower on the chart. Thats a very interesting discovery!

It is!! Are you still cranking units out in about the same time as before?

It seems that the scheduler works better as I got 13 new tasks in 12hrs one batch of 7 and one batch of 6. There are 4 tasks due to be completed still, so this is a more standard behavior that what 6.6.x was doing. My Ralph backlog is down to 1 and it ran Einstein for a bit to catch up the debt and now is back to high priority on 2 Rosie tasks that are due tomorow. Then I have a 5 day lead time on the next 4 in line. Seems that the scheduler is working better. Average cores temps run from 156-158 down from the upper 160's. So as I said, about a 10 deg. F drop. One core always runs a bit hotter than the other but it only spikes above 160 for a few seconds. I am using speedfan to monitor the core temps. Low temp on one core goes down about the 150 mark while the other stays pretty tight around the 158 mark. Still lower than before.

That sounds like it should be the new default for Boinc!! More units in the cache, scheduler is better, no slowdown in crunching AND it runs cooler on top of all that!

last 24 hrs: 1 set of 7 tasks then 12 hr wait and then one set of 6 tasks and 11 and half hrs wait and then 1 task after 6hrs wait, 2 tasks after 1 hr wait and then the last was a single task at 1 hr and 20 mins.

no back log of waiting to report.

messages log shows consistent regular requests for work for all projects.
ralph is done for the moment so just rosie and einstein doing work.

temperatures rarely approach the 165f mark on my system.
Highest temps are 163 and lowest is 157 on average.
this is with some heavy OC and a special heat sink with big fans.

the "new" 6.6.x was creating scheduling nightmares and running my temp 5-10 deg. F hotter.