Complex RelativeLayout-based View - performance issue

Got a performance issue when lots of nested RelativeLayouts are used.

For example if we have some RelativeLayout as a UI root, and every container(button, label, textview, imageview) is a RelativeLayout + Android based component (ex. aButton = RelativeLayout + ImageView + TextView), then in a complex view of 4 buttons, 3 images and 6 labels we get ~15 nested RelativeLayouts.

RelativeLayout has a very complex onMeasure method, that calculates size of every child to determine the size of layout. Calculating size of a complex view of 15-20 nested RelativeLayouts costs ~5 seconds, that's too much. onMeasure is most expensive of all calls, even drawing finished much faster then measurement. <=UPD=>

To prevent appearing suggestions to use native android views to build something complex:

Ability to add everything to everything is required. That's why every container has to be not just View, but ViewGroup. And RelativeLayout features like gravity and alignment can also help alot, that's why lot's of RelativeLayouts are used. <=/UPD=>

Had anyone got these performance problems?

Should replacing RelativeLayout with some other Layout solve issue?

Or removing all these nested layouts is the only way to deal with the problem?

Does anyone know h开发者_运维百科ow much layouts can be nested without some performance problems appearing?

It definitely depends on your testing device. But you should check the hierarchyviewer (within the tools directory) for unneccessary nests of views in order to remove them.

Also your aButton sounds like a stock ImageButton. So you could replace at least that with a standard solution.

If you posted some code it might be easier to tell whether there are more items that could be replaced by stock solutions.

After a few tests came to conclusion that having more that 12 nested layouts does a great impact on performance.
On average 10-11 nested layouts should work fine.
For example 12 nested layouts with 12 children on each display in 6 seconds on device, and in 9 on emulator.

It was my understanding that the whole point of relativelayout is that you don't have to nest them to the nth degree. Why not just use a few RelativeLayout s rather than 1 per component?