it takes 9s to extract stats from 20 samples. After profiling this method, I found 50% percent of time was for spike calculation (which calls flowViz routine, timelineplot). and the rest of the time was mainly for MFI calculation.
So the conclusion is that we should not expect getQAStats as flash fast method since it is dealing with lots of raw data calculation instead of simple stats collection.
Solution would be moving MFI calculation to c++ parser if necessary. hack into timelineplot routine to optimize it.
it takes 9s to extract stats from 20 samples. After profiling this method, I found 50% percent of time was for spike calculation (which calls flowViz routine, timelineplot). and the rest of the time was mainly for MFI calculation.
So the conclusion is that we should not expect getQAStats as flash fast method since it is dealing with lots of raw data calculation instead of simple stats collection.
Solution would be moving MFI calculation to c++ parser if necessary. hack into timelineplot routine to optimize it.