Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add timings for high level actions #462

Closed
jeanouii opened this issue May 30, 2023 · 1 comment · Fixed by #470
Closed

Add timings for high level actions #462

jeanouii opened this issue May 30, 2023 · 1 comment · Fixed by #470

Comments

@jeanouii
Copy link
Contributor

When using the Eclipse Transformer on WAR/EAR files where it takes a very long time (30 min to hours), it's frustrating to not have any visibility on what's happening.

Usually, the quiet mode is too quiet, the verbose is useless for significant WAR/EAR and the trace not relevant and even slower and unsuable.

I was wondering what I could do to optimise, and the first thing I wanted to look at is the time it takes at least per WAR (in the EAR) and per JAR. Not sure it's too useful to display class/resource level timings for now

@jeanouii
Copy link
Contributor Author

jeanouii commented Jun 5, 2023

Adding some context here ....

I have 3 applications (WAR/EAR etc).

application1 (51MB)

  • Default Eclipse Transformer run takes 10 mins
  • Excluding jars not updated makes it run in 3min30s

application2 (72MB)

  • Default Eclipse Transformer run takes 33 mins
  • With Exclusions, it takes now around 20 mins

application3 (1+GB). It has a lot of resources (properties, web pages, and so one, and of course a lot of jars)

  • Default Eclipse Transformer run takes several hours (stopped after a night)
  • With exclusions, it takes around 2 hours

@bjhargrave bjhargrave linked a pull request Jun 7, 2023 that will close this issue
bjhargrave added a commit that referenced this issue Jun 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant