in my case, indexing speed is limited by the speed of a single CPU core.
As far as I can see, the indexing process just utilizes 1 core. Depending on the current CPU load, the indexing time may vary.
As stated by support team in case #02112247 there is no possibility of optimizing this behaviour.
Therefore my feature request: Multiple threads for the indexing process.
Use case: The incremental backup of our multi TB Fileservers takes just some minutes. The incremental indexing process takes up to 5 times that backup time.
Of course I understand that multiple threads would put load on the guest VM. But with proper priority settings for this process, that should not be an issue.