As it stands today, the Data Anomalies tab will spin and spin before eventually timing out if the Customer Info object houses over 100K records. 



If a customer has more than 100k records in the Customer Info object, the first query on the data anomalies page will fail out but will load successfully after multiple refreshes.



Two queries from debug logs and their query plan from Developer console from Customer org below:



SELECT JBCXM__Account__c FROM JBCXM__CustomerInfo__c GROUP BY JBCXM__Account__c HAVING COUNT(Id) > 1 LIMIT 2000;



https://gainsight.zendesk.com/attachments/token/31VUMob2IrbBQkvhJxHXyFE4Q/?name=inline-1056425679.png​



SELECT Name FROM JBCXM__CustomerInfo__c WHERE JBCXM__Account__r.JBCXM__CustomerInfo__c = NULL LIMIT 2000;



https://gainsight.zendesk.com/attachments/token/fiV11TBn4b0IXTc0BWlNQKqIp/?name=inline763077935.png​



It appears there is a cache implemented within the page here that could use some improving.



Please do let me know of any questions.



Thanks!