We have a large Connections deployment, with over 400,000 communities, many with over 100,000 members. The communitymembership task, if indexed daily takes 4.5+ hours. If we do it weekly, it can take over 16 hours to complete. This makes it difficult to manage our search indexing schedule, and causes indexing jobs to backlog when it runs longer than expected. The task does not appear to factor in large sites in its design. Please consider redesigning this task so that it performs better when run against deploys with a large number of communities and members.