g.fillPath Much Heavier Under Multiple Paint Call Flag

This is more a question than anything – but I’ve just been testing more the new rendering option on 7.0.1 – it looks great on the UI however the CPU is much higher for me.

It’s kind of difficult understand so I’m hoping someone could shed some light. – the stack trace of what pieces of my UI are heaviest to draw are completely different with this flag on or off – for example a .fillPath which barely registers when using async coregraphics – is 30% of the CPU with this flag on.

I was under the impression that this was using async coregraphic rendering in little cache buffers which they get swapped on the UI? Is there any explanation of exactly how / what changes with the rendering when these are on?