Sonar

Way to greatly improve Memory and CPU usage on Maven plugin side

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: 1.10
  • Fix Version/s: None
  • Component/s: Maven Plugin, Tuning
  • Labels:
    None
  • Number of attachments :
    1

Description

See the attached screenshot.

Each time a Maven plugin is called by the Sonar Maven plugin (Checkstyle, PMD, Findbugs, Cobertura, ...), a new MavenSession is created in the org/sonar/batch/DefaultMavenPluginExecutor.java but creation of a new MavenSession is VERY CPU and Memory intensive as all the dependency graph and jar are analyzed.

Issue Links

This issue depends upon:
SONAR-1265 Compatibility with Maven 3.0 Major Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Freddy Mallet added a comment -

This improvement is useless with SONAR-1426 (Sonar 2.2)

Show
Freddy Mallet added a comment - This improvement is useless with SONAR-1426 (Sonar 2.2)
Hide
Permalink
Evgeny Mandrikov added a comment -

Freddy, is it tested? And is it means that with SONAR-1426 memory and CPU usage was improved in Sonar 2.2 ?

Show
Evgeny Mandrikov added a comment - Freddy, is it tested? And is it means that with SONAR-1426 memory and CPU usage was improved in Sonar 2.2 ?
Hide
Permalink
Freddy Mallet added a comment -

The resolution is "Won't Fix". Indeed, with SONAR-1426 the goal is to avoid use of Maven so working on this performance improvement is perhaps worthless.

Show
Freddy Mallet added a comment - The resolution is "Won't Fix". Indeed, with SONAR-1426 the goal is to avoid use of Maven so working on this performance improvement is perhaps worthless.

People

Vote (1)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.