I'm suprised the memory consumption would be that much higher then some of the later steps (and the final step of detecting points), but obviously I'm unfamiliar with that side of the code. On the current machine for 2587 images it took 1 hour 3 minutes to detect points, and 1 hour and 51 minutes to select pairs and match (I believe it was one hour and 51 minutes respectively). Which is the only reason I'm looking to speed that up.
The workflow has moved into reconstructing depth at the moment, (no GPU attatched), and I'm only seeing 75-80% CPU usage, is this the same behavior? (and if so this would be really nice to be able to modify it here, as I'm looking at 21 hours, 40 minutes to build depth, when it could be leveraging 20% more CPU.