Lifecycle report performance issue and replication lagDescriptionIt is expected that the lifecycle report will take a few hours to finish on large customer instances. The report generation job deletes and recreates rows in the lifecycle report every run because the job has to aggregate data from many tables that might change frequently (install, software model, etc). It is expected that the customers might see replication lag on the lifecycle report table as the job deletes and recreates rows. The issue is alleviated in Vancouver since we longer insert rows if a lifecycle has no installs.Steps to Reproduce Symptoms: Lifecycle report scheduled job taking a few hours to complete; replication lag on the lifecycle report tableWorkaroundSlowness of the job and replication lag are expected. The issue is alleviated in Vancouver since we longer insert rows if a lifecycle has no installs. Customers can decrease the frequency of the scheduled job if needed.Related Problem: PRB1595154