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

Seeing if we can speed up spotbugs #4988

Merged
merged 2 commits into from
Aug 14, 2019
Merged

Seeing if we can speed up spotbugs #4988

merged 2 commits into from
Aug 14, 2019

Conversation

JonathanGiles
Copy link
Member

@JonathanGiles JonathanGiles commented Aug 14, 2019

by lowering the effort and not forking the JVM for each module.

Fixes #4974

@JonathanGiles
Copy link
Member Author

/azp run java - core

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@JonathanGiles JonathanGiles marked this pull request as ready for review August 14, 2019 05:47
@JonathanGiles JonathanGiles self-assigned this Aug 14, 2019
@JonathanGiles
Copy link
Member Author

This shaves about 25 seconds off of the Analyze job, so I think it is worth merging.

pom.client.xml Outdated
@@ -164,12 +164,13 @@
</dependency>
</dependencies>
<configuration>
<effort>Max</effort>
<effort>min</effort>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should run nightly builds with max or more and publish the results here

Min does very little and may not catch some issues.
https://spotbugs.readthedocs.io/en/stable/effort.html

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My expectation is even at min we should get everything we want.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But I should add, there was almost no difference between min and max on my machine. The only win was from not forking the JVM for each module, so I am also happy to return this to max.

@mitchdenny
Copy link
Contributor

/azp run java - core

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@JonathanGiles JonathanGiles merged commit f173ae0 into Azure:master Aug 14, 2019
@JonathanGiles JonathanGiles deleted the spotbugs-speed branch August 14, 2019 22:54
pull bot pushed a commit to test-repo-tih/azure-sdk-for-java that referenced this pull request Aug 14, 2019
* Seeing if we can speed up spotbugs by not forking the JVM for each module
pull bot pushed a commit to test-repo-billy/azure-sdk-for-java that referenced this pull request Aug 14, 2019
* Seeing if we can speed up spotbugs by not forking the JVM for each module
pull bot referenced this pull request in AzureSDKAutomation/azure-sdk-for-java Aug 14, 2019
* Seeing if we can speed up spotbugs by not forking the JVM for each module
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 this pull request may close these issues.

Evaluate options to make spotbugs run faster - start with "effort"
3 participants