Bad Performance due to Issue Count recalculation in ManageFilters and FilterPickerPopUp

I request that the filterpicker.jsp and the managefilters.jsp not populate the issue count on the server side and instead return the page without the issue count and have it filled in later asynchronously like the Favorite Filters portlet in Jira 3.13.

I've cloned this from JRA-16959 which was resolved as a duplicate. I agree that the Favourite Filters portlet performs well as of 3.13.

The ManageFilters screen and the FilterPickerPopup window launched from portlet configuration are still very slow. Our Manage Filters screen takes about 15 seconds to load. It takes about 45 seconds to load the My tab in Manage Filters. The Filter Picker Popup takes about 15 seconds to load as well...until I disabled the issue count column in the JSP...after which it loads instantly.

And in JRA-8106, Vincent notes that he encounters similar some performance problems with Issue Filer Management which are not related to JRA-16959. He writes,

In our instance, as Administrator, I am able to see many Filters (8 filters per Project and more than 200 projects).
Due to theses figures, in JIRA 3.10, I did use any more the Filter Portlet.
Since JIRA 3.13.x, I encounter the same performance problems, for the Portlet (normal !) but also for the ManageFilters page.
It appears a priori that each filter is systematically executed in order to provide the Issue count.

May we consider an enhancement of these two features (Portlet and ManageFilters page), where Issue count are calculated periodically and stored in order to have the figures as estimate values, but not systematically recalculated.