Testing NGUI for production project. GC issues

[wallabie]

I'm at a very critical  testing stage of the project that I'm working on with NGUI and running into some serious GC issues.

Here's a screen shot of the deep profiler.

https://dl.dropboxusercontent.com/u/48378123/NGUI_GCProblem.jpg

Edit: The setup is 3 panels that are toggled using 3 tabs.  Each panel contains 2-4 scrollViews and other basic UI controls like labels and buttons.

The screenshot doesn't show the rest of the 1.2mg of GC.  but essentially, UiPanel.Find seems to be the problem.

[Nicki]

It's been said before, and I'll repeat it here for good measure. If you're running deep profiler, your results are tainted. If you're running in the Editor, your results are tainted.

You can only use them as yard sticks, not as representations of how it will run outside the development environment.

Try making a PC/mac build and connect the profiler (not deep profiler) to that running exe and see if the same problems are there. I'll bet you that the GC is almost if not all gone and the ms is significantly lower.

This is not to belittle your results or concerns, but the editor shows it far worse than it really is.

[wallabie]

@Nicki,

I agree that the deep profiler running in the editor is quite misleading.  Generally, I've been using it as a first step to get a rough estimate and not the actual numbers. Thanks for the recommendation to get the most accurate figures for NGUI. 

Edit:  I used the profiler on the device and got much better numbers.  Most of the GC figures are mostly gone. 

Cheers.