For once I'm getting a couple lol.. 3 today so far

....
Wingo I haven't heard about falling outside the qualifying. Could you please explain what you mean by it folder sign the 10% qualifying mark. I am aware about you have to return a certain number of tasks for the run-time corresponds more within reason to how long the task will actually run

I'm not to sure if I'll explain this right, but I'll have a go at it until Richard or someone else chimes in.

Your estimated run times will not settle down for AP's until you have completed 10 (or is it 11?) of them with 10% or less blanking (over 10% don't count) which is why people like being wingmates to these rigs that havn't established their proper APR's yet as they pay near what we use to get before CreditNew was introduced instead of the 40-45% of we get now for them (mind you we use to get paid the equivalent amount of credit doing MB's over the same time, though we'd do more of them).

Cheers.

Thank you for your response. I think it is once the 10th result has validated. I didn't take into consideration the blanking per work unit

---

For once I'm getting a couple lol.. 3 today so far

Bugger, I didn't get you for a wingman there either. LOL

But I did score a rookie for 1 of mine (maybe I should buy myself a lottery ticket as that's a very rare event). ;-)

Cheers.

This rig isn't a dedicated cruncher. I have to make a living somewhere along the line to feed my SETI habit.
Al the others crunch 24/7, SETI only., BOINC stock. Only background app is antivirus.

---

This rig isn't a dedicated cruncher. I have to make a living somewhere along the line to feed my SETI habit.
Al the others crunch 24/7, SETI only., BOINC stock. Only background app is antivirus.

Make sure that you have your antivirus set to ignore your BOINC folders (constant scanning of these folders is resource hogging and unnecessary), but as to the question in your PM someone here might popup with an app_config.xml that will help you to reserve a core on your rigs as I use a very old version of BOINC so I use an app_info.xml instead to do that.

Cheers.

4 so far for the 24 Feb 2018 UTC.

And 4 more turned up taking the total to 8 for the day.

Cheers.

ap_07fe18ae_B6_P1_00314_20180220_09916.wu:

818.18 credits.

Looks like your new wing man theory holds true....he joined Dec 17.
I had a little over an hour in the file, wingman had almost 14.

---

This rig isn't a dedicated cruncher. I have to make a living somewhere along the line to feed my SETI habit.
Al the others crunch 24/7, SETI only., BOINC stock. Only background app is antivirus.

Make sure that you have your antivirus set to ignore your BOINC folders (constant scanning of these folders is resource hogging and unnecessary), but as to the question in your PM someone here might popup with an app_config.xml that will help you to reserve a core on your rigs as I use a very old version of BOINC so I use an app_info.xml instead to do that.

Cheers.

Simplest since you are using a new enough Manager and Client would be to set a project_max_concurrent in an app_config that restricts the number of tasks running at any time. That along with a ncpu and ngpu usage parameter in the app_config would restrict the number of cpu tasks running alongside the gpu tasks. The ideal configuration results in cpu tasks having a cpu_time equal to the run_time which is when a system is not overcommitted in cpu usage.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

This rig isn't a dedicated cruncher. I have to make a living somewhere along the line to feed my SETI habit.
Al the others crunch 24/7, SETI only., BOINC stock. Only background app is antivirus.

Make sure that you have your antivirus set to ignore your BOINC folders (constant scanning of these folders is resource hogging and unnecessary), but as to the question in your PM someone here might popup with an app_config.xml that will help you to reserve a core on your rigs as I use a very old version of BOINC so I use an app_info.xml instead to do that.

Cheers.

Simplest since you are using a new enough Manager and Client would be to set a project_max_concurrent in an app_config that restricts the number of tasks running at any time. That along with a ncpu and ngpu usage parameter in the app_config would restrict the number of cpu tasks running alongside the gpu tasks. The ideal configuration results in cpu tasks having a cpu_time equal to the run_time which is when a system is not overcommitted in cpu usage.

I supplied him with an app_config.xml that should work this morning so we'll see how it goes. ;-)

Cheers.

Only picked up 1 AP total of 4 today which is excellent for me as normally miss out lol..

Its now loaded on all 12 systems running SETI, so let u see what percolates.

My thanks to all.

v/r,
Mike

---

Its now loaded on all 12 systems running SETI, so let u see what percolates.

My thanks to all.

v/r,
Mike

I'll take a look at your CPU task times tomorrow to see if they improved, but your 4 core CPU's should now only be running 3 CPU tasks instead of 4 if it worked.

Cheers.

ap_09fe18ac_B5_P1_00305_20180223_13032.wu:

909.93 credits.

---

Its now loaded on all 12 systems running SETI, so let u see what percolates.
My thanks to all.
v/r,
Mike

I'll take a look at your CPU task times tomorrow to see if they improved, but your 4 core CPU's should now only be running 3 CPU tasks instead of 4 if it worked.

I just had a look at your rigs and only 7865348, 8399579 and 8424289 are still showing signs of over commitment, but the rest are looking good.

Cheers.

Fresh 1's are being delivered again.

Cheers.

Even though the creation rates on the SSP have been missing here all day I've managed to pickup 8 10 so far.

Cheers.

"0" zip, nadder and zilch here :(

I'm still waiting on that rookie from the other day to complete their AP task, but I hit the jackpot this time today with 4 of them allocated to rookies. :-D

Cheers.

Just got 1 AP now :}

A real lucky day today, 17 20 now across my 2 rigs.

Cheers.