Canvas.PrepareBatchesJob destroying performance?

Hello, I'm using Unity 5.2.2 in iOS , and I get huge spikes 20ms range, coming from WaitingForJob, Canvas.PrepareBatchesJob that happen at irregular intervals. I'm using World Space Canvas. Is there anything I can do to cut this down? My UI doesn't even do much, it mostly sits there, with the occasional fading or scaling animation.

 

If I deactive the UI I get 200 fps, with it, I barely can get 30 fps.. I notice even if even one ui component is on the screen animating in anyway it goes into a frenzy from 200 to 30ps.

Edit: doesn't even need to animate...

 

The waiting for job issue came up about a week ago, someone else posted a topic about it. I ran into the same issue and did my best to file a defect for it but if you have a really simple repo case for it, then feel free to submit a bug.

 

I wish I did, its part of something much larger I can't rip out easily. Oddly, its only affecting this one scene, I'm not seeing other scenes with this. Also funny too, which it says 20ms for WaitingForJob, if you drill down to the PrepareBatchesJob, it says its only .2 of that..but doesn't show me the function where its mostly at. I noticed a few of the frames also had 'SortJob' under that too but it was alot rarer. Thanks for the link though I feel alot better knowing I might not be the only one...

 

It's the same for us. It's really tough to nail down a cause of this because the profiler doesn't seem to show all the information we need. I just hope somebody at Unity is looking into hunting this down, because we are kind of at a loss at this point.

If anyone from Unity is seeing this, I believe we sent our full project to Sam Bickley semi-recently to help investigate a different issue occurring on PS4. If you've got contact with him or have access to the project drop FTP, look for a drop from Hellfire Games. That drop should experience the WaitingForJob issue under some circumstances. If you need help repro'ing it in our project, send me a PM or email. We can possibly upload the project again if necessary, but it's very, very large, so we'd rather not have to upload it again, if we can get away with it. Alternatively, I might be able to set you up with repo access so you can pull down the latest yourselves overnight or something.

 

Let me know if they start to looking into this.. At this point I'm way too far into 5.2 to go back to 5.1.