PsiStore operations on very big stores leads to running out of memory.

I have a 2 hour length, 426 GB PsiStore. As part of my post study process, I wanted to remove a stream and save the store in another location for deep storage. The code is basically as following:

var outputStorePath = Path.Combine(@"D:\Hallway-Recording-Clean", datasetID, sessionID);
PsiStore.Copy((partition.StoreName, partition.StorePath), (partition.StoreName,outputStorePath), null, s => s.Name.Contains("ir"), false);

When I run the code, the memory usage slowly goes up and eventually my system run out of memory (I have 64 GB of RAM) and the application crashes. I think I could just change the pipeline to use real time which should work but it means I have to wait 2 hours for it to finish.

Is there any ways to make the system run as fast as possible without reading the store so fast that it runs out of memory? Thanks!

Start with the PsiStore.Copy call shown in the report and inspect how the stream filter processes very large stores. Reproduce the copy using a large store or the reported 426 GB scenario, then determine whether memory remains bounded while copying only the selected streams. Done means the operation completes without exhausting available memory and does not require real-time playback.