If you haven't yet discovered it, use CEViewer. That might help pin point
which collection(s) might be taking a long time to evaluate--causing others to
wait and wait and wait. Once you find which collection(s) might be taking
minutes instead of seconds to eval; you can either figure out if you need them
at all anymore; or look at the coll query and determine if someone did bad
wql--for example using like '%something' in a where statement, or some kind of
Mobius strip of references causing SQL to spin and spin.
"only 60 collections with incremental updates" --that feels like a lot
actually, IMO. You 100% sure you need all of those to be incremental?
On Wednesday, February 10, 2016 10:01 PM, Hun boy <[email protected]>
wrote:
We have collections updates issues, if I update collection membership or
imported any machine it is taking around 4 hrs to actual reflection.. I could
see collection evaluator log always busy.
We have only 60 collections configured with incremental updates and remaining
all collection are configured as full updates every 7 days.
Total we have 1000+ collections with only 5000 devices count.
Any pin points on this ?? How others are managing this collections setup??
Sent from iPhone....sorry for typos
