Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Anisotropy performance fluctuates wildly #241

Open
rimadoma opened this issue May 6, 2020 · 2 comments
Open

Anisotropy performance fluctuates wildly #241

rimadoma opened this issue May 6, 2020 · 2 comments

Comments

@rimadoma
Copy link
Contributor

rimadoma commented May 6, 2020

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.

@rimadoma rimadoma self-assigned this May 6, 2020
@rimadoma
Copy link
Contributor Author

rimadoma commented May 6, 2020

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.

@rimadoma
Copy link
Contributor Author

rimadoma commented May 6, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant