You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The time Anisotropy takes fluctuates randomly between runs. For example, I've seen bat_cochlea_volume.zip take anything between 10 000 and 40 000 ms with the default parameters (directions = 2_000, linesPerDirection = 10_000, samplingIncrement = sqrt(3.0)). Ideally performance would be more consistent.
The text was updated successfully, but these errors were encountered:
I thought if sometimes MIL sampling was unlucky, and had a lot more misses than at other times. This is not the case, in fact I found out that sometimes execution takes less time with fewer iterations:
Duration: 18169 ms
Iterations: 112817664
Misses: 63958158
Duration: 13345 ms
Iterations: 112901391
Misses: 64139667
I also checked that the total length of the lines sampled is always the same.
I checked with VisualVM that it's not garbage collection kicking in. It's not. What I did notice is that on slower runs CPU usage fluctuates more from the usual ~95 %. Almost all the execution time is spent in ParallelLineMIL.countPhaseChanges() which is to be expected.
The time Anisotropy takes fluctuates randomly between runs. For example, I've seen bat_cochlea_volume.zip take anything between 10 000 and 40 000 ms with the default parameters (
directions = 2_000, linesPerDirection = 10_000, samplingIncrement = sqrt(3.0)
). Ideally performance would be more consistent.The text was updated successfully, but these errors were encountered: