To be honest for example taking the iterator for a period of 6 hours and then looping through the results can basically already be over 1500us in the profiler on instinct watches. I'm really trying to avoid to do any thing that can cause noticable lag on Instinct watches. But with the history iterator it pretty much seems unavoidable and best thing I can do is to only run this loop at moments there's the least change a user would try to do something else like going to glances view or something. But I just don't like that there's always that slight chance where the iterator loop runs and the user might be wanting to do something else at the same time..
Wonder how you guys running through the iterator if it generates so many results the loop will take so long it actually creates noticable delay?
