Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » Resolution / Materialization / Build times
Resolution / Materialization / Build times [message #762427] Wed, 07 December 2011 22:27 Go to next message
Philip Bedingfield is currently offline Philip Bedingfield
Messages: 42
Registered: August 2011
Member
I have a cquery that materializes and builds all our products at once. Starting with a clean workspace it takes roughly 13 minutes in eclipse, and 90 minutes headless via Jenkins. My question is why does it take so long headless, isn't the process the same?
I don't think I'm not doing anything different. My Buckminster commands are simply ->

importtargetdefinition -A '${WORKSPACE}/.../tmis.all.target'
addbaseline -A "TMIS All Target"
import '${WORKSPACE}/.../tmis.all.cquery'
build

We are using cvs which is slow, but I would expect the load on cvs to be the same in the ide as headless.

Any help appreciated.
Re: Resolution / Materialization / Build times [message #762690 is a reply to message #762427] Thu, 08 December 2011 09:10 Go to previous messageGo to next message
Matthew Webber is currently offline Matthew Webber
Messages: 198
Registered: December 2010
Senior Member
This is more a general impression than hard data, but I also see a difference in build times, with the IDE faster than the command line. Materialization appears to take a simialar amount of time.

Could it be something to do with the amount of memory available to each process?
Re: Resolution / Materialization / Build times [message #762894 is a reply to message #762690] Thu, 08 December 2011 14:23 Go to previous message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3214
Registered: July 2009
Senior Member
On 2011-12-08 15:10, Matthew Webber wrote:
> This is more a general impression than hard data, but I also see a
> difference in build times, with the IDE faster than the command line.
> Materialization appears to take a simialar amount of time.
>
> Could it be something to do with the amount of memory available to each
> process?
>
Buckminster will utilize the runtime as an artifact repository. If the
exact right artifact is found there, then it will be copied rather than
downloaded. The IDE runtime contains a lot more stuff than the headless
one. That might explain some of the difference.

- thomas
Previous Topic:Building Javadoc of multiple projects
Next Topic:Can Buckminster headless launch a *.launch file for external tools?
Goto Forum:
  


Current Time: Thu Jul 31 13:50:01 EDT 2014

Powered by FUDForum. Page generated in 0.02547 seconds