I've manipulated the utilization factor many times over the years to keep my GPUs fully utilized, so I think I understand how it works, but, I'm not getting the behavior I expect from O3AS. Can some one please advise?
I was surprised by and missed the original announcement about FGRP1BG going away, and got caught; FGRP1BG the only E@H app I had turned on. I noticed a few days ago and turned on O3AS and other apps. Now, I'm trying to optimize the utilization factor for these unfamiliar apps.
For FGRP1BG (and other apps), I have tried values of 1, 0.5, 0.32, and 0.25 in the past, and got 1, 2, 3, and 4 concurrent tasks, respectively, as expected. So, it not only makes mathematical sense, I think I know what to expect from personal experience. It looks like 0.5 is about right for BRP7, but just 2x O3AS concurrent tasks is not enough for full utilization, so I set it to 0.33, then 0.32, then 0.3, updating the project each time, and I'm still only getting 2 O3AS concurrent tasks. What am I missing?
(I'm going to try 0.25, now. But, I don't understand why I haven't seen any effects from my previous settings changes?)
Thanks in advance.
Copyright © 2024 Einstein@Home. All rights reserved.
Yeah, and I see this in the
)
Yeah, and I see this in the log:
So, it's pretty clear that O3AS is NOT getting it's utilization factor from the GW GPU setting. Doesn't that seem wrong?
O3AS doesn't seem to respond
)
O3AS doesn't seem to respond to any of the configurable utilization factors. I'm really confused. It must be fixed?
Ah I think I figured it out.
)
Ah I think I figured it out. I haven't received any new tasks, so, even though I have changed the computing settings *and* updated the project, my cache is full, and the FAQ about utilization factor says that value will only take affect when new WU are downloaded.
...Hmm, I've tried increasing my cache, but that's not working. It says "no new tasks" is selected, but it is clearly not. Still confused.
Yeah, okay. It took 72
)
Yeah, okay. It took 72 hours, but finally got some new O3AS WUs and the new GW utilization factor took effect, as promised in the fine print.
Funny. I had this same
)
Funny. I had this same problem again just about on year later. Glad I made a note here *because I completely forgot the solution*.