FlexBuilder / MXMLC: Profiling the build process?

I noticed that recently FlexBuilder assemblies take much longer than before (30 or 40 seconds, unlike 3 or 4). What is the easiest way to profile these collections to find out what takes a lot of time?

+3
source share
3 answers

Have you tried to clean your project? (Project → Clean)

From Adobe Live Docs: Performing a Clean Build

After a project has been built, subsequent builds affect only the resources that have been added  
or modified. To force the Flex Builder compiler to rebuild all resources in a project, you can 
perform a clean build. You might perform a clean build if, for example, you want to eliminate all 
potential sources of a problem you encountered when testing your application.

    1. Select Project > Clean from the main menu.
    2. Select the project (or projects) whose build files you want to discard and rebuild from scratch.
    3. Click OK.
+1
source

, Flex Builder java, 500M, , Flex Builder , . , , Window- > Preferences, " " " ".

, , html-template. , .

Evenrything html- bin-debug , . , , - .svn .cvs html- .

+1

FlashBuilder - , eclipse - Java. eclipse JProfiler. . trakc down, waht , , , . ,

-incremental=true

. , "-Xms" "-Xmx".

, . -XX: PermSize = -XXMaxPermSize =. GC, permspace.

And if you play with these variables, always make sure that they are actually used. It happens more than just to put them somewhere (batch file, exlipse.ini) with them having any effect.

+1
source

Source: https://habr.com/ru/post/1731902/


All Articles