Ticket #5062 (assigned)

Opened 9 years ago

Last modified 5 years ago

CropWorkspaces takes too much memory

Reported by: Peter Peterson Owned by: Peter Peterson
Priority: major Milestone: Backlog
Component: Framework Keywords:
Cc: Blocked By:
Blocking: Tester:

Description

While working with large event workspaces the fact that CropWorkspace makes a copy of the data when doing the crop in-place is really an issue as it temporarily doubles the memory usage.

Change History

comment:1 Changed 9 years ago by Peter Peterson

  • Owner set to Peter Peterson
  • Status changed from new to assigned

comment:2 Changed 9 years ago by Peter Peterson

Refs #5062. Added erase method to EventList.

This is really just used by CropWorkspace::execEventInplace

Changeset: af04d23561a79dc2bc019ba958bcfe12e7bd63d9

comment:3 Changed 9 years ago by Peter Peterson

Refs #5062. Modified erase method so it actually releases memory.

Changeset: d77c309cc237efc3902cf791a205fb8c83d3d50d

comment:4 Changed 9 years ago by Peter Peterson

Refs #5062. Added events in-place branch to CropWorkspace.

Changeset: 3337361c16a8205788ed0830a37fdab3274fce32

comment:5 Changed 9 years ago by Peter Peterson

Refs #5062. Temporarily disabling new code.

Changeset: feed060c3f5b92681b700ea7e39eb272a03824f3

comment:6 Changed 9 years ago by Peter Peterson

Refs #5062. Deleting erase method since it did not help.

Changeset: a0e2914d23660693494f2f23f848e136658e504c

comment:7 Changed 9 years ago by Peter Peterson

Refs #5062. Folded inplace lessons learned into execEvent.

Changeset: ade45f275e648838edba6277a239a612674e5823

comment:8 Changed 9 years ago by Janik Zikovsky

Refs #5062: fix NormaliseToMonitor which was broken by CropWorkspace

Reverted to old inefficient method. Something must be a little off in the new way...?

Changeset: f6ce98ccf214bee9e3fc2073d91b44dacf7117c2

comment:9 Changed 8 years ago by Nick Draper

  • Milestone changed from Release 2.1 to Release 2.2

Moved at end of release 2.1

comment:10 Changed 8 years ago by Nick Draper

  • Milestone changed from Release 2.2 to Release 2.3

Moved at the end of release 2.2

comment:11 Changed 8 years ago by Nick Draper

  • Milestone changed from Release 2.3 to Release 2.4

Moved to milestone 2.4

comment:12 Changed 8 years ago by Peter Peterson

  • Milestone changed from Release 2.4 to Release 2.5

comment:13 Changed 7 years ago by Nick Draper

  • Milestone changed from Release 2.5 to Release 2.6

Moved to r2.6 at the end of r2.5

comment:14 Changed 7 years ago by Nick Draper

  • Status changed from assigned to new

comment:15 Changed 7 years ago by Nick Draper

  • Component changed from Mantid to Framework

comment:16 Changed 7 years ago by Nick Draper

  • Milestone changed from Release 2.6 to Backlog

Moved to backlog at the code freeze for R2.6

comment:17 Changed 7 years ago by Nick Draper

  • Status changed from new to assigned

Bulk move to assigned at the introduction of the triage step

comment:18 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​5908

Note: See TracTickets for help on using tickets.