Uploaded image for project: 'FishEye'
  1. FishEye
  2. FE-3553

Disable multiple print for Perforce repository

    • Icon: Bug Bug
    • Resolution: Answered
    • Icon: High High
    • None
    • None
    • None
    • None
    • FishEye 2.3.5 on Linux

      We're using FishEye 2.3.5, linked to Perforce 2010.1 and we found "Disable Multiple Print" for our perforce repositories, makes worse performance. But we had to enable it due to the following bug:
      https://jira.atlassian.com/browse/FE-2710

      What's the status of this bug? Can we enable multiple print now?

      Thanks,
      --Jack

          Form Name

            [FE-3553] Disable multiple print for Perforce repository

            Owen made changes -
            Workflow Original: FE-CRUC Bug Workflow [ 2944658 ] New: JAC Bug Workflow v3 [ 2956702 ]
            Owen made changes -
            Workflow Original: FECRU Development Workflow - Triage - Restricted [ 1517366 ] New: FE-CRUC Bug Workflow [ 2944658 ]
            Owen made changes -
            Workflow Original: FECRU Development Workflow - Triage [ 941224 ] New: FECRU Development Workflow - Triage - Restricted [ 1517366 ]
            Piotr Swiecicki made changes -
            Workflow Original: FECRU Development Workflow (Triage) [ 307686 ] New: FECRU Development Workflow - Triage [ 941224 ]
            mwatson made changes -
            Resolution New: Answered [ 9 ]
            Status Original: Needs Triage [ 10030 ] New: Closed [ 6 ]

            mwatson added a comment -

            Guys,

            I'm going to close this - please re-open the issue if you find any issues with the multiple print option.

            Thanks for you help with this,
            Matt

            mwatson added a comment - Guys, I'm going to close this - please re-open the issue if you find any issues with the multiple print option. Thanks for you help with this, Matt

            mwatson added a comment -

            Mark: Good to hear it's working better for you - keep us posted
            Jack: I would recommend upgrading to 2.6.2 before you try to renable multi-print. If you are having issues upgrading, consider raising a support request at https://support.atlassian.com

            Thanks,
            Matt

            mwatson added a comment - Mark: Good to hear it's working better for you - keep us posted Jack: I would recommend upgrading to 2.6.2 before you try to renable multi-print. If you are having issues upgrading, consider raising a support request at https://support.atlassian.com Thanks, Matt

            We're at Crucible/FishEye 2.6.2. I've gone back and forth between 32-bit and 64-bit Java - but currently on Java 1.6.0_26 / 64-bit with options:

            -Xms1900m -Xmx1900m -XX:-UsePerfData -XX:+UseCompressedOops"
            

            Crucible/FishEye is definitely a pig - and the only reason I have it limited to 1900m above is due to the machine it is on being low on RAM even with 8 GB of RAM. It is currently on a virtual machine that it shares with Bamboo, Nexus, and PostgreSQL (dedicated for Crucible/FishEye and Bamboo). We might be moving it to its own virtual machine shortly.

            During some upgrades - I believe I did need to temporarily set a higher heap space value - but not lately.

            I know it's trouble as we have gone through it ourselves - but I have found the performance improvements worth the effort to upgrade to latest Crucible/FishEye.

            Mark Mielke added a comment - We're at Crucible/FishEye 2.6.2. I've gone back and forth between 32-bit and 64-bit Java - but currently on Java 1.6.0_26 / 64-bit with options: -Xms1900m -Xmx1900m -XX:-UsePerfData -XX:+UseCompressedOops" Crucible/FishEye is definitely a pig - and the only reason I have it limited to 1900m above is due to the machine it is on being low on RAM even with 8 GB of RAM. It is currently on a virtual machine that it shares with Bamboo, Nexus, and PostgreSQL (dedicated for Crucible/FishEye and Bamboo). We might be moving it to its own virtual machine shortly. During some upgrades - I believe I did need to temporarily set a higher heap space value - but not lately. I know it's trouble as we have gone through it ourselves - but I have found the performance improvements worth the effort to upgrade to latest Crucible/FishEye.

            Which version FishEye are you using? We are still using 2.3.5.
            We have some trouble to upgrade FishEye.
            Are you using 32-bit JVM or 64-bit JVM?
            We have OutOfMemeory with 32-bit JVM and Xmx2048m

            Thanks,
            --Jack

            jack.zhao@emc.com added a comment - Which version FishEye are you using? We are still using 2.3.5. We have some trouble to upgrade FishEye. Are you using 32-bit JVM or 64-bit JVM? We have OutOfMemeory with 32-bit JVM and Xmx2048m Thanks, --Jack

            I went ahead and ran it on all the remaining Perforce repositories we have. They are smaller and completed in only a few hours. Although there were warnings - they are the same as the ones I already listed earlier, just in new contexts.

            We had Disable Multiple Print enabled in response to an actual issue in the past. Unless the users report a problem - I see no evidence that the problem still impacts us.

            Jack: Are you game to try? It looks like this issue may be fixed?

            Mark Mielke added a comment - I went ahead and ran it on all the remaining Perforce repositories we have. They are smaller and completed in only a few hours. Although there were warnings - they are the same as the ones I already listed earlier, just in new contexts. We had Disable Multiple Print enabled in response to an actual issue in the past. Unless the users report a problem - I see no evidence that the problem still impacts us. Jack: Are you game to try? It looks like this issue may be fixed?

              Unassigned Unassigned
              4ef58e65d61d Jack
              Affected customers:
              2 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: