"Close Projects" to improve compilation performance in Flex Builder
DIGG IT!
3
Comments
Published
Sunday, January 14, 2007
at
11:43 AM
.
In Flex Builder if you leave projects open, the incremental compiler will compile "Open Projects" in the background at start-up and save. I keep seeing developers complain of slow start-up/compilation of Flex Builder and 95% of the time they have 10+ projects open. Ahhhhhhhhhhh......
Here is what to do:
In "Navigator" panel, Right-click on the Project Folder and "Close Project"
Close the Flex projects that you are not working on and you will see Flex Builder performance take off! Otherwise when you press save on any project, Flex will check each project to see if compilation is required. By having a project open, you are making Eclipse do a ton of work in the background and use a ton of resources.
If someone complains about Flex Builder start-up or compilation:
Ask them "How many Projects do you have open?"
Cheers,
ted :)
Great advice!! I noticed this for the first time today, as I was working, I decided I didn't need all those test projects I had made, and closed them all, what a difference!
Thanks a lot!
FWIW, a future improvement to Flex Builder... in Windows you might consider using a FileWatcher class to watch all the source files for the many open projects. Then, on recompile, only recompile projects where you've been notified the source has changed (rather than, I assume, polling all the file date stamps).