Flex 4 considerably slower than Flex 3
We are working on a client-server based visualization system. Our client is written in flex and comprises two main views: A design view that shows a flow diagram where users define modules and module relations, and a semantic view that shows the visualization views.
The client was originally written in Flex 3, naturally we want to use Flex 4 right now. However, when switching to Flex 4, throughout the application we experience major performance losses. To quantify this we have picked a representative client action: The switching from the semantic view to the design view (only one is visible at a time, see my short video:
http://old.vrvis.at/download/hiaMoh4M/flex4issues.mp4 ).
We use a fade effect for the transition between these two states, however, the fade effect starts very delayed if we go for Flex 4 without the Flex 3 compatibility mode.
We did timings for 4 cases:
1. Flex 4 with Flex 3 compatibility mode: 828 ms, this is ok
2. Flex 4 without Flex 3 compatibility mode, using the old mx components: 3759 ms => this is a real problem, 3 times slower, why is this?
3. Flex 4 without Flex 3 compatibility mode, replacing most of the mx containers (boxes) with the Flex 4 related versions (groups) , Halo theme => 3500ms, no improvement
4. Flex 4 without Flex 3 compatibility mode, like before, replacing most of the mx containers (boxes) with the Flex 4 related versions (groups) , but the Spark theme => 8460ms, what's going on here?
Here are the details about our test system:
Prozessor: AMD Athlon 64 X2 Dual Core 4400+ 2.21 GHz
RAM: 4.00 GB
Windows XP x64 Service Pack 2
Using Adobe Air 2.0.
I know that we are extensively using nested boxes for our layout (this is very convenient), but why is Flex 4 performing so much worse than Flex 3? Is there something we could be doing completely wrong?
Thanks much for your help,
Jurgen
