Opened 13 years ago

Closed 12 years ago

#121 closed defect (fixed)

Reconstruction too memory-hungry

Reported by: MatthewWhiting Owned by: MatthewWhiting
Priority: normal Milestone: Release-1.2
Component: Wavelet reconstruction Version: 1.1.12
Severity: normal Keywords:
Cc:

Description

Need to look closely at the memory usage of the reconstruction.

For instance, there is at least one needless allocation of the full size of the image - we don't need the residuals to be stored in an array. What would be better would be to have additional functions in getStats.cc that calculate the statistics of the differences between two arrays.

Note that the getMedianStats etc have an *additional* allocation of memory, so the way we are doing it now is to allocate an array, then allocate it again to find the stats. And that's all we do with that memory. Needless duplication.

We need to look in more detail at how the algorithm is implemented, as I'm sure there are other savings that can be achieved here.

Change History (2)

comment:1 Changed 12 years ago by MatthewWhiting

Milestone: Release-1.2Release-1.1.14
Status: newassigned

Some of this work has been done - look at what remains and see if the work for 1.1.14 is sufficient to close the ticket.

comment:2 Changed 12 years ago by MatthewWhiting

Resolution: fixed
Status: assignedclosed

The work for this ticket appears to be all done, so closing.

Note: See TracTickets for help on using tickets.