| impact of excessive warnings on project build time [message #1770303] |
Wed, 09 August 2017 15:56  |
Eclipse User |
|
|
|
I'm trying to help out someone who has asked about long build times they get with Neon and Oxygen but not Mars. Code is roughly 1 million lines, 10 years old and generates many warnings (4000 +). On Mars, build is about a minute, and a "clean all" adds another 15 seconds. Neon and Oxygen however take 10 minutes + to run on the same code. It seems to hang at some point but he can't identify any particular part of the code where the hang happens.
I'm speculating that there might be some sort of "big 0" issue on the warning generation. For example, maybe when warnings are generated, references are made to the entire set of warnings generated up to that point in order to add some useful aspect to the warning. But I don't really know anything about what goes on under the hood for Eclipse when compiling or cleaning projects.
Curious that the issue goes away with Mars. Any thoughts on what is different and what might be done to allow the newer Eclipse builds to work better with the project. (The problem may have nothing at all to do with the warnings.)
If I get some leads here, I will provide the friend with this link and allow him to continue the discussion.
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.52628 seconds
Home