Issue Details (XML | Word | Printable)

Key: JRA-8106
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Lars
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

Implement configuration option on saved filters portlet

Created: 30/Sep/05 01:40 PM   Updated: 24/May/06 12:05 AM
Component/s: Portlets
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Participants: Lars and Scott Farquhar [Atlassian]
Since last comment: 3 years, 1 week, 1 day ago
Labels:


 Description  « Hide
The saved filters portlet doesn't perform very well in large installations because the issue count is shown for each filter.

If you have a large amount of filters, a count is performed for each filter. This makes the page where the portlet is shown load slower than necessary.

May i suggest that you implement a configuration option on this portlet so that the user can select if the number of issues for a filter should be shown together with the filter name or not.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Scott Farquhar [Atlassian] added a comment - 03/Oct/05 05:38 PM
Lars,

That is a good idea.

Can I ask which version of JIRA you are running, and how many different filters there are? I'm trying to get an idea of how slow this page is for you.

If you turn profiling on, and attach the log file - that would help me.

Cheers,
Scott


Lars added a comment - 05/Oct/05 01:42 PM
Scott,

Currently we run 3.3.1.

The user can se about 4000 issues at this moment.


Lars added a comment - 05/Oct/05 01:49 PM
Whoops,

Here is the rest of the comment

The user has about 30 filters. Page load was not a problem, but the count is unnecessary in our opinion. Of course the user deleted most of the filters before i has time to make a profile. So here is one with just 6 filters... it don't know if this is usable for you.

 
Oct 5, 2005 8:38:52 PM org.apache.catalina.core.StandardWrapperValve invoke
INFO: PROFILED : 0 keys (0 unique) took 0ms/250912ms : 0.0% 

Oct 5, 2005 8:38:52 PM org.apache.catalina.core.StandardWrapperValve invoke
INFO: [79ms] - /secure/admin/jira/ViewLogging.jspa

RESULT GROUP: PERMISSIONS
  1:0ms 11-wmxxxxx-Project [0]
  1:0ms 10-wmxxxxx-Project [0]
  4:0ms 0-wmxxxxx [0,0,0,0]
PERMISSIONS: 6 keys (3 unique) took 0ms/79ms : 0.0% 0ms/query avg.

PROFILED : 6 keys (3 unique) took 0ms/79ms : 0.0% 0ms/query avg.

Oct 5, 2005 8:38:58 PM org.apache.catalina.core.StandardWrapperValve invoke
INFO: [1813ms] - /secure/Dashboard.jspa
  [47ms] - PortletColumn
    [47ms] - Running portlet: /portlets/dashboard/projecttable.jsp
  [1688ms] - PortletColumn
    [1438ms] - Running velocity portlet: 10002
      [938ms] - Permission Query
      [47ms] - Lucene Search
      [78ms] - Lucene Search
      [31ms] - Lucene Search
      [31ms] - Lucene Search
      [32ms] - Lucene Search
    [141ms] - Running velocity portlet: 10003
      [63ms] - Lucene Query
        [63ms] - Lucene Search
      [47ms] - IssueManager.getIssue()
      [15ms] - IssueManager.getIssue()
      [16ms] - IssueManager.getIssue()
    [94ms] - Running velocity portlet: 10004
      [63ms] - Lucene Query
        [63ms] - Lucene Search
      [15ms] - IssueManager.getIssue()
      [16ms] - IssueManager.getIssue()

RESULT GROUP: PERMISSIONS
  1:0ms 11-wmxxxxx-Project [0]
  229:31ms 10-wmxxxxx-Project [0,0,15,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,16,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]
  7:0ms 0-wmxxxxx [0,0,0,0,0,0,0]
PERMISSIONS: 237 keys (3 unique) took 31ms/1813ms : 1.7098732% 10ms/query avg.

PROFILED : 237 keys (3 unique) took 31ms/1813ms : 1.7098732% 0ms/query avg.