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

Performance improvement for IntegrateEllipsoids #12562

Closed
VickieLynch opened this issue May 7, 2015 · 3 comments
Closed

Performance improvement for IntegrateEllipsoids #12562

VickieLynch opened this issue May 7, 2015 · 3 comments
Assignees
Labels
Framework Issues and pull requests related to components in the Framework Stale This label is automatically applied to issues that are automatically closed by the stale bot

Comments

@VickieLynch
Copy link
Contributor

This issue was originally TRAC 11724

Looking at the performance tests, I’ve noticed that the change to run IntegrateEllipsoids in parallel has yielded an decrease in speed. See http://builds.mantidproject.org/view/Tests/job/performance_tests_master/Master_branch_performance_tests/ MDAlgorithmsTest.IntegrateEllipsoidsTestPerformance.test_execution_events
Conceptually, doing this part of the processing in parallel should not have had this effect. For 3.5 do you think you could profile the performance tests on this algorithm to find out where the real bottle necks are?

@VickieLynch
Copy link
Contributor Author

@VickieLynch (2015-05-13T12:00:08):
Refs http://trac.mantidproject.org/mantid/ticket/11724 more changes for thread safety

8e5d4a8


@VickieLynch (2015-05-28T12:21:17):
Refs http://trac.mantidproject.org/mantid/ticket/11724 fix spelling

8870bbd

@VickieLynch VickieLynch added the Framework Issues and pull requests related to components in the Framework label Jun 3, 2015
@VickieLynch VickieLynch self-assigned this Jun 3, 2015
@VickieLynch VickieLynch added this to the Release 3.5 milestone Jun 3, 2015
@VickieLynch VickieLynch modified the milestones: Release 3.6, Release 3.5 Sep 14, 2015
@VickieLynch VickieLynch removed this from the Release 3.6 milestone Jan 17, 2016
@stale
Copy link

stale bot commented Feb 24, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you feel this is incorrect please comment to keep it alive, with a reason why.

To prevent closure, e.g. for long-term planning issues, add the "Never Stale" label.

@stale stale bot added the Stale This label is automatically applied to issues that are automatically closed by the stale bot label Feb 24, 2021
@stale
Copy link

stale bot commented Mar 3, 2021

This issue has been closed automatically. If this still affects you please re-open this issue with a comment so we can look into resolving it.

@stale stale bot closed this as completed Mar 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Framework Issues and pull requests related to components in the Framework Stale This label is automatically applied to issues that are automatically closed by the stale bot
Projects
None yet
Development

No branches or pull requests

1 participant