Re: [jdt-dev] Measuring the build time for a workspace

[Mickael Istria <mistria@xxxxxxxxxx>]

Hi Lars,

In https://github.com/mickaelistria/eclipse-ide-parallel-builds-demo/tree/master/org.eclipsecon.demo.parallelbuilds which I'm using to test/demo parallel builds, there is a feature to generate build time consumption Gantt chart for JDT projects.

It uses the logged info as you enabled and presents a view of it.

Hth

On Wednesday, September 26, 2018, Lars Vogel <lars.vogel@xxxxxxxxxxx> wrote:

Friends of JDT,

I would like to measure how long the JDT builder needs to build a
certain workspace.

I activated debug/builder/stats in the tracing options of
org.eclipse.jdt.core. Afterward, I clean the whole workspace and
trigger a full build (auto build is turned off).

I then look that the "in" numbers per project, e.g., in 981ms in the
following example.

>FULL BUILD STATS for: org.eclipse.core.commands
>   compiled 12789 lines in 981ms:13036.6lines/s
>   parse: 219 ms (22.3%), resolve: 392 ms (39.9%), analyze: 57 ms (5.8%), generate: 141 ms (14.3%)

Is this the correct way of doing it? Or do you have a better way?

Best regards, Lars

--
Eclipse Platform project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vogel@xxxxxxxxxxx, Web: http://www.vogella.com
_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jdt-dev

--

Mickael Istria

Eclipse IDE developer, for Red Hat Developers