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

Check performance implication of tracking breakpoints #2122

Open
jeromekelleher opened this issue Nov 8, 2022 · 1 comment
Open

Check performance implication of tracking breakpoints #2122

jeromekelleher opened this issue Nov 8, 2022 · 1 comment

Comments

@jeromekelleher
Copy link
Member

We currently track all breakpoints during the simulation using an AVL tree. We should profile once #2121 is done and see if this is a significant amount of our time.

If it is, we can make the recombination breakpoint tracking optional and turn it on in the places that we use it in our statistical tests.

@GertjanBisschop would you mind reporting back on what the perf report for a large simulation is wrt to breakpoint tracking?

@jeromekelleher
Copy link
Member Author

Ah, we also use this in mspms so that we have strict compatibility with ms. So, we would need to turn it on for this application.

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