-
Type: Improvement
-
Status: Resolved
-
Priority: Minor
-
Resolution: Won't Fix
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BlobManager
-
Tags:
-
Team:PLATFORM
-
Sprint:nxplatform next
-
Story Points:2
Some lag has been observed on blob/gc computation while reading the source/blob stream populated by high deleted blob events.
It should be fast because there is nothing to do, it looks like the check is not optimized:
In the normal case the canDelete flag is not persisted and evaluated on each blob