We are developing a large scale image editing application using Flex. The company we hired suggested that we use Flex as it is best for image editing.
Unfortunately, the only thing holding us back from release is that the application is suffering from serious performance issues that the programmers cannot resolve. I don't have any experience in Flex (or programming in general) but it would be greatly appreciated if anyone could offer some tips that I could pass on to the team...
The application is separated into five different "sections". Each section contains a large amount of tools such as image effect overlays, textures, borders etc., including the standard revert, crop, undo, redo tools that you would expect to find. Even without any images imported, skipping between these pages will take 5-10 seconds. Once images are imported, the program will completely bog down and almost become unusable.
I've opened up task manager and checked the usage, and even with the application idle, it is using 300mb. This seems relatively high compared to CS5 which is only using 30mb. I don't really know if this proves anything but I thought I'd mention it anyway.
If the developers are using FlashBuilder, there is a profiler they can use
to find out where that time is going and guide where to optimize. There are
several released image editors written in Flex.
Are they using modules ? How many and how big are the images ? 300 MB worth of images comes out to be 100 high-quality images , but that's still alot. I don't even know how to make Flash take up 300MB without stuffing it with tons and tons of images and holding references to each and every last one of them. Which brings the point , are they holding references to images that are no longer needed ?