Should we poll cpu/core count?

[breedx-splk]

The number of processors available to the runtime is not static, and can change over the lifetime of an application launch or user session:

https://developer.android.com/reference/java/lang/Runtime#availableProcessors()

Would it be helpful to generate an event when the number of cores changes? Wouldn't a change in CPUs be potentially VERY impactful to application performance? Would RUM implementations be able to (eventually) use this event to denote that something interesting changed in the hardware/cpu provisioning?

[fractalwrench]

My guess is that listening for changes in Thermal Status and Power Save mode would correlate strongly with this return value.

[breedx-splk]

My guess is that listening for changes in Thermal Status and Power Save mode would correlate strongly with this return value.

Oh interesting. It sounds like it would. Are you suggesting then that rather than polling on a schedule, we could then only poll when we receive these callbacks? Cool idea!

[fractalwrench]

My assumption is that those would be more useful signals to capture than CPU/core count as they indicate a reason for why performance might be degraded. CPUs should also get throttled/disabled in both those scenarios so availableProcessors() would probably change.

Both thermal status/power save mode do have callback APIs so as you've said, it would be better than polling on a schedule