Is there any way to decrease time of GC reachability analysis?

Two-faced · March 3, 2020, 4:40pm

Or maybe turn on multithreading for that? Here is our environment:

[2020.03.03-14.14.01:541][762]525369
Objects (Total: 550.295M / Max:
570.108M / Res: 943.941M | ResDedSys: 95.668M / ResShrSys: 0.000M / ResDedVid: 721.755M / ResShrVid:
0.000M / ResUnknown: 126.518M)

[/Script/Engine.GarbageCollectionSettings]
gc.MaxObjectsNotConsideredByGC=10000
gc.SizeOfPermanentObjectPool=6000000
gc.CreateGCClusters=True
gc.NumRetriesBeforeForcingGC=4
gc.MaxObjectsInEditor=46229396
gc.MaxObjectsInGame=16777216
gc.AllowParallelGC=True
gc.IncrementalBeginDestroyEnabled=True
gc.ActorClusteringEnabled=True
gc.BlueprintClusteringEnabled=False
gc.MultithreadedDestructionEnabled=False
gc.UseDisregardForGCOnDedicatedServers=False

Two-faced · March 13, 2020, 9:53am

bumping…

JakubMFG · July 24, 2023, 12:20am

bumping…

JakubMFG · July 25, 2023, 8:09am

Adding

[/Script/Engine.GarbageCollectionSettings]
gc.ActorClusteringEnabled=True

to the bottom of /Game/Config/DefaultEngine.ini

and manually enabling CanBeInCluster on relevant Actors should help