Ticket #79 (closed defect: fixed)

Opened 4 years ago

Last modified 3 years ago

Code path optomisation

Reported by: cjax Owned by: Joel
Priority: major Milestone: Eraser 6.1/6.2
Component: BlackBox Version:
Keywords: Cc:
Processor Architecture: Blocked By:
Blocking: Operating System:

Description

If you walk through the current code it will be observed that we create a list of files to be removed more than once. This is waist of CPU and indeed it slows the startup time of an erasure task.

This should be improved by changing the code path so we get maximum of one call for the GetPaths? ... functions.

Blocking

IdSummaryMilestone
#79└ Code path optomisationEraser 6.1/6.2

Blocked by

IdSummaryMilestone
#79└ Code path optomisationEraser 6.1/6.2

Change History

comment:1 Changed 3 years ago by Joel

  • Status changed from new to accepted
  • Owner set to Joel
  • Component set to BlackBox

comment:2 Changed 3 years ago by Joel

  • Status changed from accepted to closed
  • Resolution set to fixed

As of r2104 GetPaths? is only called once, after the moving of the erasure targets to the default plugin.

Note: See TracTickets for help on using tickets.