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

[BUG] Very slow compilation on Eclipse 2019.03 with Lombok 1.18.10 #2352

Open
vmi opened this issue Feb 3, 2020 · 3 comments
Open

[BUG] Very slow compilation on Eclipse 2019.03 with Lombok 1.18.10 #2352

vmi opened this issue Feb 3, 2020 · 3 comments

Comments

@vmi
Copy link

vmi commented Feb 3, 2020

Describe the bug
Compiling about 5000 files takes 15 minutes on Eclipse with Lombok agent.

To Reproduce
Sorry, because it is proprietary software, I cannot put out the reproduction information.

Expected behavior
Compile faster than in the current status.

Version info (please complete the following information):

  • Lombok 1.18.10
  • OpenJDK Runtime Environment (build 1.8.0_242-b07) / OpenJDK 64-Bit Server VM (build 25.242-b07, mixed mode)
  • Eclipse IDE for Java Developers
    • Version: 2019-03 (4.11.0)
    • Build id: 20190314-1200
    • OS: Windows 10, v.10.0, x86_64 / win32
    • Java version: 1.8.0_242

Additional context

I applied a patch ( perftest.patch.txt ) to lombok 1.18.10 and got a log ( lombok.zip ).
The log format is as follows.

  1. Value of System.nanoTime()
  2. PatchFixesHider.transform_swapped() execution time (ns)
  3. Target file name (anonymized)
  4. Source start position
  5. Source end position

When the logs were totaled, the following results were obtained:

  • compilation time: 897.4 sec
  • sum of transform_swapped execution time: 1051.0 sec
  • number of calls and total execution time for each file ( total-each-files.txt )

I think that the slowdown is caused by the same file being processed too many times.

@hheg
Copy link

hheg commented Feb 15, 2020

@vmi I may experience the same problem and trying to figure out if this is the same problem. If I may ask, do you have the CodeMining feature activated when this happens?

@vmi
Copy link
Author

vmi commented Feb 17, 2020

@hheg I don't use CodeMining.
I analyzed this issue on 2019.03, but I have found this problem in older Eclipse too.
At least this has happened in Eclipse since 4.6 Neon.

@hheg
Copy link

hheg commented Feb 17, 2020

@vmi Ok, I don't remember when they included CodeMining in Eclipse, but IIRC I have the problem I experience with at least 2019-12 and 2020-03-M1.

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

No branches or pull requests

2 participants