Eclipse Community Forums: Buckminster » Resolution / Materialization / Build times

Help

Home

Home » Archived » Buckminster » Resolution / Materialization / Build times

Show: Today's Messages :: Show Polls :: Message Navigator

Resolution / Materialization / Build times [message #762427]

Thu, 08 December 2011 03:27

Philip Bedingfield

Messages: 43
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.

Report message to a moderator

Re: Resolution / Materialization / Build times [message #762690 is a reply to message #762427]

Thu, 08 December 2011 14:10

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?

Report message to a moderator

Re: Resolution / Materialization / Build times [message #762894 is a reply to message #762690]

Thu, 08 December 2011 19:23

Thomas Hallgren

Messages: 3240
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

Report message to a moderator

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

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 18:50:24 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter