@kazink Sorry for the confusion this causes. Yes, this certainly sounds like a processing time issue. We need to do a better job of communicating that the software backend is still in the middle of processing data (perhaps with a proper progress bar). I’ll let the team know this.
The fact that you are able to run the measurement much quicker on a smaller data set gives the clue that processing time could be the reason here.
What happens when you incrementally increase the size of the measurement box? Do you notice the time to process slowly increase as well?