CPU Usage and DFP Bannerview

[Cody Rotwein]

I just started noticing a consistent 3 to 4% CPU usage (using Xcode's Debug navigator) after a DFP banner view gets called and displayed. 

It happens both on iOS 7 and 8, and using latest Admob SDK and the previous version of the SDK. 

The CPU stays at 3 or 4% once the ad is called. This can't be normal and will obviously have consequences on the battery.

Anyone else seeing this behavior? 

[Cody Rotwein]

I just confirmed that some kind of bug was introduced starting with Admob SDK 6.11.1. Both 6.11.1 and 6.12.0 cause CPU to stay at 2 to 4% once a DFP bannerview is loaded.

When I go back to Admob SDK version 6.9.1, CPU stays at 0% once an ad is loaded. For now, I'm going to be using this version of the Admob SDK until the issue is resolved.

[Yogesh Joshi]

I couldn't find any way to download the older SDK versions.

Do you know where can I get them?

[Cody Rotwein]

Hi Yogesh,

I just sent you an email with the 6.9.2 version. Let me know if you're seeing the same thing.

[Yogesh Joshi]

Thanks Cody.

Yes, I'm seeing the same.

In fact with 6.12.0, there is small but noticeable lag at the start when [DFPBannerView alloc] initWithAdSize: is called.

Yogesh Joshi

[Eric Leichtenschlag]

Alright, I've filed a bug against engineering to investiage the CPU difference on 6.12 vs 6.9.2.

As for why DFPBannerView is slower on iOS 8, although 6.12 made some improvements in this area, the iOS 8 UIWebView appears to be slower.

[Cody Rotwein]

Any update on this?

[Eric Leichtenschlag]

Can you try running 6.12.0 again and see if you get better results? The SDK was able to flip a switch that doesn't require an SDK release that should improve the performance drop you noticed.

Thanks,
Eric

[Cody Rotwein]

Still seeing a consistent 2% CPU usage.

[Eric Leichtenschlag]

So, to confirm, it's better than before but still not ideal?

[Cody Rotwein]

Yes, that's correct.

--

---
You received this message because you are subscribed to a topic in the Google Groups "Google AdMob Ads Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/p6KsjbBIrEw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Eric Leichtenschlag]

Ok, the change in the SDK that is having an effect on CPU is essentially active view, to track if the ad is visible on the screen. This is an important metric for advertisers, so removing it is simply not an option. We've already started experimenting with turning down how frequently we check if the ad is visible (hence the improvement you saw), and we'll try to reduce further as long as the feature still can work reliably. Wherever that happy medium is, you'll have to deal with the small performance difference. The upshot is in the long run, this metric improves advertiser confidence, which increases their bids, which translates into higher eCPMs for pubs.

Yes, that's correct.

To unsubscribe from this group and all its topics, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.