And no more OPNG came in...........the kitties just launched those 29 8671s. We'll see how long this lasts.
Meowmeowmeow. Munchmunchmunch.

Meow

EDIT......
Oh boy, this does not look good. First one ran for 3:03 and done. 2nd one ran for 3:42. 3rd one, 3:20. 4th, only 2:45. And that's on the kitties' single GTX980, not a real powerhouse.

Again no work for my 3 Titans, crying....crying

That message will disappear after the first opng-task you get.

I'm back to the occasional bundles of GPU tasks. It's working well enough that I don't feel a need to worry about it, and with scarce GPU tasks instead of a continuous supply, I've renamed my app_config.xml out of the way and gone back to 15 CPU tasks.

As an aside, one thing about going back to the small batches of GPU tasks is that it levels the playing field at least somewhat. Even a modest GPU can crank out plenty of work. No need to break the bank for an RTX 3080, assuming you can even get one.



This is what I was using before going back to one GPU task. This is on a Ryzen 7, 14 CPU tasks allocated by Computing Preferences, and a GTX 960 running two tasks.

<app_config>
   <app>
      <name>opng</name>
      <max_concurrent>2</max_concurrent>
      <gpu_versions>
          <gpu_usage>.5</gpu_usage>
          <cpu_usage>.25</cpu_usage>
      </gpu_versions>
   </app>
</app_config>

The max_concurrent setting might not be necessary, but I use it as insurance.

Well, no GPU tasks at all since the stress test ended. Shutting down my main GPU cruncher.