Documentation for GreenHopper 4.3.x . Documentation for other versions of JIRA Agile is available too.
GreenHopper is now called JIRA Agile. Learn more.

Here is a list that may help you to improve your GreenHopper performance:

  • First, make sure your gzip compression from the JIRA -> 'Administration' -> 'Global Settings' -> 'General configuration' is set to 'on'.
  • GreenHopper will play with more then one issue at the same time. Your JVM will then require more Memory then JIRA standalone. We strongly recommend to have at least 512 MB of RAM allocated to your JVM.
  • Since GreenHopper is displaying and building the statistics for all unreleased versions make sure to release your versions once they are done.
  • Use the filters or contexts if you are updating a lot of issues.
  • In your context the default sort by option is 'Natural' sorting. This is very heavy sorting that regroups task and subtasks. If you have a lot of issues this sorter can be very slow. We strongly suggest that you select a GreenHopper ranking field instead (make sure that the 'Number Searcher' is selected as the 'Search Template'), this one is indexed therefore very fast.
  • Avoid adding to much fields in your issue card templates — Remember that all the information needs to travel on the wire...
  • Avoid unlimited text field in your card templates.
  • You can configure your server to add an Expires or a Cache-Control Header
  • If using Firefox please read this Knowledge Base article about resolving performance issues when using GreenHopper with Firebug.

Some users have reported that the performance of GreenHopper can be very poor on a VMWare. They have increased their performance significantly by installing JIRA and GreenHopper on a standalone server.

See Also

  • No labels





Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.