Uploaded image for project: 'Forge'
  1. Forge
  2. FORGE-2670

Command-completion is slow

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Major
    • 3.x Future
    • 3.2.3.Final
    • None
    • None
    • Hide

      Type "comm"; press TAB. Wait ~2 seconds for UI to respond.

      Show
      Type "comm"; press TAB. Wait ~2 seconds for UI to respond.

    Description

      When typing e.g. "comm" and hitting Tab, it takes approximately 2 seconds for the command-completion to kick in and make suggestions/complete the command.

      I have written about it already here: https://developer.jboss.org/message/960679#960679
      Not sure what best to provide to make analysis easier. I am also Ok with debugging it myself if there maybe is a pointer in the right direction where to look into.

      Regarding the questions in the forum post:

      • I did not run any previous commands; it was this way from the beginning. I also deleted the ~/.forge folder to start afresh. Same issue
      • I used the forge console from within eclipse and from the cmd. Both the same.
      • I am using the 3.2.3 Final version

      I have attached a screenshot of the jvisualvm sampler. Steps i did:
      1. Type "com"
      2. Start sampler
      3. Type "TAB"
      4. Wait for command-completion
      5. Stop sampler

      It took approximately ~2 seconds for the command-compeltion to respond. it seems the extensive checks like DefaultFileOperations.fileExists are a big part of it as it accumlates to ~1 seconds which sound much.

      Attachments

        1. jforge.png
          jforge.png
          151 kB
        2. out.txt
          75 kB
        3. threaddumps.txt
          68 kB

        Activity

          People

            rhn-support-ggastald George Gastaldi
            38leinad Daniel Platz (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: