com.google.android.gms.ads.omid.library.walking.xx keep running

[Raymond Chan]

Hi support,

I found that these calls trigger from time to time and taking around 1x% of CPU resources even when user is not interacting with the app. Is it expected that these calls are running from time to time? If so, any ways to optimize them? This doesn't look good as it's taking already 1x% of resources even when user is not interacting with the app but just putting in foreground.

Attached you may find the CPU trace.

AdMobSDK: 19.1.0

[Mobile Ads SDK Forum Advisor Prod]

Hi Raymond,

Thank you for bringing this to our attention.

I was only able to look at the first screenshot, assuming I should be looking at the green highlighted callback. I was wondering if you could send the stack trace in a different extension. I was unable to view it.

Also if possible can you send any other information that might help us to better understand the issue. From what I can tell you have the SDK implemented and are able to get the Ads as you expect? Just from what you saw on the processing raised an alarm because there seems to be a unnecessary/high usage of CPU.

Regards,
William Pescherine
Mobile Ads SDK Team

Regards,
William Pescherine
Mobile Ads SDK Team

ref:_00D1U1174p._5004Q1zpWWp:ref

[Raymond Chan]

Hi William,

Can you try to open the trace file with Android Studio 3.6?

Yes, app is able to get the ads expected. I was asking this is because I found that there's a function (as in the trace) that keeps running constantly when

the app is put in foreground even user doesn't have any interaction with it. These calls are taking 1x% of CPU resources from time to time.

[Mobile Ads SDK Forum Advisor Prod]

Hi Raymond,

I work along with William. Would it be possible for you to provide the project as well? This will greatly help us on our investigation. Once shared, I'll also raise this to the rest of the team to get their insights as well. Kindly use the Reply privately to author option to share the details privately.

Regards,
Teejay Pimentel

[anton.aver...@gmail.com]

In our project we see lots of invocations of omid.walking implementations, each trying to do Display.getRealSize that looks to be quite expensive, taking up to 90ms of CPU time in the main thread.

Same issue we see with AppNexus implementation of TreeWalker.

Is there maybe a way to cache getRealSize values and not calculate it every time every frame?
Basically with ads enabled, our app performance is absolutely ruined.

[anton.aver...@gmail.com]