When watcher start, the CPU (112%) and energy impact are very high, please see attached.
Is it possible to reduce the resources when cloud session start to query anchors ?
I am using the default sample to test performance issue.
Thanks for looking closer into this. In the title you mention you're using CoarseRelocation. Do you get the same high energy and CPU impact if you search with CoarseReloc turned off in your query?
When watcher start, the CPU (112%) and energy impact are very high, please see attached. Is it possible to reduce the resources when cloud session start to query anchors ? I am using the default sample to test performance issue.