Viewing results is slow while job is in progress, if --no-non-hits-in-stream
If a large indexing job is run via the GUI with --no-non-hits-in-stream, the majority of frames (depending on hit rate) will not be in the streams at all. Unfortunately the GUI will interpret this as meaning that the indexing job has simply not reached that frame yet. So, it re-scans all the streams every time the frame is changed. This makes it very slow.