Bug #265

Hashing delay should be implemented in the backend core

Added by George Notaras almost 2 years ago. Updated almost 2 years ago.

Status:Closed Start date:04/12/2010
Priority:High Due date:04/14/2010
Assignee:George Notaras % Done:

100%
Category:Backends Spent time: 0.75 hour
Target version:0.1.7 Estimated time:1.00 hour

Description

It seems that the hashing delay should be implemented inside the file_paths() generator as it currently possible has no effect while file contents or metadata is collected, resulting in high disk IO operations per second.

History

#1
Updated by George Notaras almost 2 years ago

  • Due date set to 04/14/2010
  • Status changed from New to Assigned
  • Assignee set to George Notaras
  • Target version set to 0.1.7
  • Estimated time set to 1.00

#2
Updated by George Notaras almost 2 years ago

  • Status changed from Assigned to Closed
  • % Done changed from 0 to 100

Tested and it seems to work as expected. Will increase the default delay to 100ms

Also available in: Atom PDF