Select to view content in your preferred language

Export Release Build - Exporting takes 20+ minutes

1050
8
Jump to solution
07-16-2012 02:22 PM
BrettElliot
Deactivated User
Hi everyone,

I've been using ArcGIS Viewer for Flex for a few months now.  The biggest issue that i've been having is that the export time takes at least 15 minutes every time I export the release build.  This can be frustrating, especially if I make a simple mistake such as a missing parenthesis, as I'll have to go back and re-compile.

Are these export times normal?  Another user in the office says his only takes 3-5 minutes to export the same projects.

Some background information:
- We are storing the project folders on a network drive
- I'm exporting the compiled application directly to our web server
- I've followed the steps outlined here: http://resources.arcgis.com/en/help/flex-viewer/concepts/index.html#/Getting_started_for_developers/...
- I'm using Flash Builder 2.6, and ArcGIS Viewer for Flex 3.0, ArcServer 10.1, and ArcGIS 10.1

Any insight to these long compile times is greatly appreciated! Thanks!
Tags (2)
0 Kudos
1 Solution

Accepted Solutions
AnthonyGiles
Honored Contributor
Brett,

The time your project takes to compile and export is effected by a number of different things, such as:

1. RAM and processing power of the machine you are on (This is probably the most important),
2. How many modules you are trying to compile (do not compile functionality that you are not using)
3. The amount of images you have in your assets/images folder remove those not required.

You should only need to export once you have a version that you want to publish. If you want to check your work as you are going along you do not need to export you can click the play button and check your work against your bin-debug version, ensure you have build automatically turn on.

Regards

Anthony

View solution in original post

0 Kudos
8 Replies
AnthonyGiles
Honored Contributor
Brett,

The time your project takes to compile and export is effected by a number of different things, such as:

1. RAM and processing power of the machine you are on (This is probably the most important),
2. How many modules you are trying to compile (do not compile functionality that you are not using)
3. The amount of images you have in your assets/images folder remove those not required.

You should only need to export once you have a version that you want to publish. If you want to check your work as you are going along you do not need to export you can click the play button and check your work against your bin-debug version, ensure you have build automatically turn on.

Regards

Anthony
0 Kudos
BrettElliot
Deactivated User
Thanks Anthony.
0 Kudos
AnthonyGiles
Honored Contributor
Brett,

Dont forget to also mark the post as answered by checking the tick on the correct answer.

Regards

Anthony
0 Kudos
MLowry
by
Frequent Contributor
While the previous answer is a very good answer and explanation in general, in order to know if 15 min. is normal we'll need some more information.


15 minutes on a non-fully customized Sample Flex Viewer 3.0 build?
You posted "I'm using Flash Builder 2.6".
Did you mean 4.6?
How many widgets/modules do you have set to compile?

Can you post your hardware specs?
0 Kudos
BrettElliot
Deactivated User
While the previous answer is a very good answer and explanation in general, in order to know if 15 min. is normal we'll need some more information.


15 minutes on a non-fully customized Sample Flex Viewer 3.0 build?
You posted "I'm using Flash Builder 2.6".
Did you mean 4.6?
How many widgets/modules do you have set to compile?

Can you post your hardware specs?


Correct, I meant to type Flash Builder 4.6.

Computer is:
Intel Xeon CPU
W2550 @ 3.07 GHz, 3.25 GB RAM,
Windows XP Professional SP3, 32 Bit.

All that has been changed with the Flex Viewer 3.0 build is the skin and modification of a few config.xml files.
It looks like there are 23 widgets/modules set to compile.  However I previously went through and removed the unused ones from the "Project>Properties>Flex Modules" menu, which hasn't made a difference.

Thanks for your insight,
0 Kudos
RobertScheitlin__GISP
MVP Emeritus
Brett,

    The time it takes to export a release build can increase if you have more than one project open in Flash Builder. So before you do an export release build make sure you right click your project and choose "close unrelated projects". This is just additional info to what Anthony post as his post is spot on.
0 Kudos
BrettElliot
Deactivated User
Thanks Robert,

I've definitely tried that too!
0 Kudos
BrettElliot
Deactivated User
Hi again Anthony,

I got a new work computer, and now it exports in <5 minutes.  It looks like it was a slow computer problem and not a software setting!

Thanks again!


Brett,

The time your project takes to compile and export is effected by a number of different things, such as:

1. RAM and processing power of the machine you are on (This is probably the most important),
2. How many modules you are trying to compile (do not compile functionality that you are not using)
3. The amount of images you have in your assets/images folder remove those not required.

You should only need to export once you have a version that you want to publish. If you want to check your work as you are going along you do not need to export you can click the play button and check your work against your bin-debug version, ensure you have build automatically turn on.

Regards

Anthony
0 Kudos