Working with a customer, and they are experiencing odd issues with compliance imports. They only manage 300 machines with bigfix, and this is an overview of the environment:
Root server was just migrated from a VM to physical that has 2x20 core processors and 128GB memory. Database is local (2016 Std edition) and is only running BES Server and Web Reports.
Compliance is a separate VM, 2x6 cores and 12GB memory. Compliance database is local and is dedicated to running Compliance.
Imports are taking 20+ hours to complete which is a little long for only 300 machines. Getting an import log from them, there are two spots where the import just hangs before moving forward.
2019-09-02 04:02:12 (+0:00:00.297) INFO: DatasourceFixlet items: 0
2019-09-02 04:02:12 (+0:00:00.031) INFO: ETL Datasource task: from ****** - DatasourceFixlet (0x00000000239284EA - 0x000000002394C10C): Success
2019-09-02 04:02:12 (+0:00:00.000) INFO: ETL Datasource task: from ******* - DatasourceGroupFixletResult (0x00000000239284EA - N/A): Start
2019-09-02 14:20:39 (+10:18:26.288) INFO: DatasourceGroupFixletResult items: 0
2019-09-02 14:20:39 (+0:00:00.031) INFO: ETL Datasource task: from ******** - DatasourceGroupFixletResult (0x00000000239284EA - 0x000000002394C10C): Success
2019-09-02 14:20:39 (+0:00:00.000) INFO: ETL Datasource task: from ******** - DatasourceGroup (0x00000000239284EA - N/A): Start
2019-09-03 00:15:22 (+9:54:43.259) INFO: ETL Datasource task: from ****** - DatasourceGroup (0x00000000239284EA - 0x000000002394C10C): Success
Those two lines seem to be accounting for 20 hours of import time, but it’s been a while since i’ve worked closely with compliance importing, so i’m not exactly sure what those lines are referencing. BigFix server is version 9.5.13 and Compliance is 1.10.1.48. Any insight into this would be awesome, thanks!