Contributor Macro is Extremely Slow to Render with Large Spaces and Contributors

Summary

Contributor macro in Confluence 6.0.6 takes 6 minutes to return results when loading the page it is on if the space it is searching contains many pages, ~17,000 pages for example, and is configured to scan descendants or children.

Environment

• Confluence 6.0.6 Data Center

Steps to Reproduce

1. Have a space with ~17,000 pages and over ~1170 contributors in the space
2. Configure the root page of the space with the contributor macro with the following options:
   Contribution Type: Authors
   Sort by: Count
   Display Format: List
   Maximum Number of Contributors: 50
   Show Count: Checked
   Show last Contribution Time: Checked
   Include Page Hierarchy: Descendants

Expected Results

When loading the page the contributor macro will display the contributors within a minute or two.

Actual Results

The page displays, but the macro does not display the contributors until 6 minutes later. Many end users do not wait and report that the macro is not working. The logs show:

2017-03-27 14:46:10,048 WARN [http-nio-8090-exec-4] [confluence.util.profiling.DefaultActivityMonitor] close Exceeded the threshold of 60000 ms: ActivitySnapshot{startTime=1490650763574, threadId=238, threadName='http-nio-8090-exec-4', userId='admin', type='web-request', summary='/rest/com.atlassian.confluence.contributors/1.0/contributors?mode=list&showCount=true&scope=children&limit=100&spaces=PROD&showLastTime=true&contextEntityId=1022429&=1490650763508'}_
– referer: https://INSTANCE_DOMAIN.com/display/USERS/Users+Home | url: /rest/com.atlassian.confluence.contributors/1.0/contributors | traceId: caf7733225cb19da | userName: admin
2017-03-27 14:47:02,920 INFO [http-nio-8090-exec-7] [confluence.rpc.auth.TokenAuthenticationInvocationHandler] invokeAuthenticatedMethod Executing remote API method [ getPage ] as user [ admin ][ admin ]

Notes

This can easily be reproduced by the customer in their environment due to the size of the space and contributors.

Workaround

There is not an available workaround.