Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Components
Assignee
Jacob Cobbett-SmithJacob Cobbett-SmithReporter
Jacob Cobbett-SmithJacob Cobbett-SmithPriority
MinorCompatibility
PointFix versions
Pull Request URL
Roadmap
Not applicableDue date
Jan 16, 2020
Details
Details
Components
Assignee
Jacob Cobbett-Smith
Jacob Cobbett-SmithReporter
Jacob Cobbett-Smith
Jacob Cobbett-SmithPriority
Compatibility
Point
Fix versions
Pull Request URL
Roadmap
Not applicable
Due date
Jan 16, 2020
Created January 7, 2020 at 4:38 PM
Updated January 23, 2020 at 10:13 AM
Resolved January 23, 2020 at 10:13 AM
File deletion can be expensive/take time on some filing systems.
Dafilesrv has the concept of normal 'fast' traffic, consisting of e.g. many read and write packets from clients and slower atypical traffic, e.g. file copy, treecopy, file append, get crc.
Currently 'remove' is categorised as part of the normal, meaning that if a series of removes take time the available concurrency slots will be occupied and normal trace (standard read/writes) will be delayed.
It would be better to re-categorise 'remove' transactions to the atypical queues, so that they can't delay standard transactions.