Wrong application sent
9 Jan 2020 23:50:15 UTC
Topic 220395
(moderation:
I have two machines I'm trying to run Einstein on (just GPU). I need different settings for each - mainly because one of them has a slow CPU and a fast GPU, so I need to avoid the gravity tasks which need a lot of CPU assistance, or the GPU is severely throttled. I've set the offending machine (called "black") to be in the "work" category, and told it not to give me gravity tasks, but it repeatedly does so.
If this page takes an hour to load, reduce posts per page to 20 in your settings, then the tinpot 486 Einstein uses can handle it.
You also need to set "Allow
)
You also need to set "Allow non-preferred apps" to "no", to prevent other tasks from sneaking in.
I tried that, and also turned
)
I tried that, and also turned everything possible off, just leaving gamma tasks. Maybe it takes a while to take effect (although I did make sure to tell the client to update). After a while, it's now getting the correct ones. Could be coincidence, could be it's now working.
Also doesn't the setting you mentioned only take effect if there are no gamma tasks available? All queues are healthy on the Einstein server just now.
It's definitely taking the correct "work" category, as it has a different priority to the other machine which is in the "default" category.
If this page takes an hour to load, reduce posts per page to 20 in your settings, then the tinpot 486 Einstein uses can handle it.
Peter Hucker wrote:Also
)
That could be. My situation was the other way round, I wanted GW tasks and no FGRP. I got FGRP tasks from time to time, but you're right, there were also problems with availability of GW work.
I'm still only getting the
)
I'm still only getting the correct gammas on the machine that doesn't like gravity. So I guess there was just a delay initially somewhere.
If this page takes an hour to load, reduce posts per page to 20 in your settings, then the tinpot 486 Einstein uses can handle it.
Peter Hucker wrote:...
)
As I understand it, the scheduler accesses a small, fast cache of tasks which is a subset of full number of available tasks. When the cache empties, it gets refilled (fairly quickly) from the full list. When the full list gets low, the WU generator kicks in to refill that.
So, there is probably a small window of opportinity - maybe seconds to a minute or two - where the scheduler, seeing a temporarily empty fast cache, could take advantage of an 'alternative application' setting - if you have allowed it to.
I don't know this for sure - only by observation. My hosts ask for work under script control. They ask sequentially, with a gap of 15-30 secs between them. I often see individual hosts being told "no work available" and then a couple of minutes later when they ask again, they get tasks. I attribute this behaviour to what I've described above.
If it's critical not to get 'alternative' tasks, then make sure you don't have that setting turned on.
Cheers,
Gary.
I straight away turned off
)
I straight away turned off alternative tasks, and it does seem to be behaving now. Something took a while to take effect on the Einstein end. Normally settings take effect as soon as my clients have contacted the server.
If this page takes an hour to load, reduce posts per page to 20 in your settings, then the tinpot 486 Einstein uses can handle it.