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

ExportSampleLogsToCSVFile performance #12375

Closed
OwenArnold opened this issue Apr 14, 2015 · 3 comments
Closed

ExportSampleLogsToCSVFile performance #12375

OwenArnold opened this issue Apr 14, 2015 · 3 comments
Assignees
Labels
Framework Issues and pull requests related to components in the Framework High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Stale This label is automatically applied to issues that are automatically closed by the stale bot

Comments

@OwenArnold
Copy link
Contributor

This issue was originally TRAC 11537

This algorithms really struggles for exporting time series logs that contain a large number of entries. Conversely if I try to export the log table as a table in MantidPlot and save it to disk it's almost instantaneous so there must be a way to get this operation faster.

I was trying this with a workspace that contained a time series log with something of the order of 1E6 entries.

The following need to be fixed.

  • There is no progress reporting
  • The algorithm execution locks-up the whole of MantidPlot
  • The execution time is far too long. I force quit MantidPlot after about 5 minutes.

Would be nice if this was fixed for 3.4 because we have users who want to export large time series logs as part of their experiment.

@OwenArnold
Copy link
Contributor Author

@wdzhou (2015-05-05T14:15:16):
The algorithm is written in python now and was not targeted for time series log with huge size. In order to improve the performance, this algorithm should be re-written in c++.


@wdzhou (2015-05-08T18:37:18):
Refs http://trac.mantidproject.org/mantid/ticket/11537. Created new files in c++.

4287a67


@wdzhou (2015-05-14T03:46:06):
Checkpointing the start of implementation. Refs http://trac.mantidproject.org/mantid/ticket/11537.

2daa000


@wdzhou (2015-05-14T03:46:07):
Checkpointing progress of translation work. Refs http://trac.mantidproject.org/mantid/ticket/11537.

18d873d

@OwenArnold OwenArnold added High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Framework Issues and pull requests related to components in the Framework labels Jun 3, 2015
@OwenArnold OwenArnold added this to the Release 3.5 milestone Jun 3, 2015
@NickDraper NickDraper modified the milestones: Release 3.5, Release 3.6 Sep 14, 2015
@NickDraper NickDraper modified the milestones: Release 3.6, Release 3.7 Jan 22, 2016
@NickDraper NickDraper modified the milestones: Release 3.7, Release 3.8 May 20, 2016
@NickDraper NickDraper modified the milestones: Release 3.8, Release 3.9 Oct 3, 2016
@NickDraper NickDraper modified the milestones: Release 3.9, Temporary Holding Oct 14, 2016
@NickDraper NickDraper removed this from the Temporary Holding milestone Oct 3, 2017
@stale
Copy link

stale bot commented Feb 23, 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 23, 2021
@stale
Copy link

stale bot commented Mar 2, 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 2, 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 High Priority An issue or pull request that if not addressed is severe enough to postponse a release. 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

3 participants