Mihir Kamdar, We should also target this test:
a. Have a continuous scan load - low latency scans
b. Have an array index and documents with large arrays (i.e.100 documents with around 5000 array entries or more)
c. Update the array entries and check the latency of scans when update is happening
Without the fix, the scan's should take more time when array updates happen. During this time, if we monitor the indexer pause due to GC, there should be a spike.
With the fix, that should not be the case - scan latencies should be normal and no spikes in indexer pause due to GC.