Uploaded image for project: 'Spring IDE'
  1. Spring IDE
  2. IDE-1064

Improve performance of classpath scanning during workspace build

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.3
    • Fix Version/s: 2.3.1
    • Component/s: None
    • Labels:
      None

      Description

      After initial discussion in the forum (see attached forum reference), I used VisualVM to grab a handful of stack dumps of STS 2.3 when it gets stuck in the "loading ..." stage of a workspace build. See attached stack dumps.

      In each case, the culprit is clear; it's the thread which is performing some heavy classpath scanning, seemingly chunking through every JAR file in the workspace classpath. It seems to be rescanning this classpath every time Eclipse's builder kicks off (e.g. changing a class's method signature, any change to a spring beans file), and for large workspaces within a couple of dozen projects and several dozen JAR dependencies, this is cripplingly slow.

      I could post some beans files also, but there are many, many of them, and finding the wood for the trees might be hard.

        Attachments

        1. stack1.txt
          22 kB
        2. stack2.txt
          26 kB
        3. stack3.txt
          24 kB
        4. stack4.txt
          23 kB

          Activity

            People

            • Assignee:
              cdupuis Christian Dupuis
              Reporter:
              skaffman Kenny MacLeod
            • Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: