-
Notifications
You must be signed in to change notification settings - Fork 50
Open
Labels
I4No visible changesNo visible changesS3Minimally significantMinimally significantU4Nothing urgentNothing urgentenhancementImproving existing functionalityImproving existing functionalityneofs-storageStorage node application issuesStorage node application issuesperformanceMore of something per secondMore of something per second
Description
Is your feature request related to a problem? Please describe.
I'm always frustrated when I'm thinking of write cache and blobstor relations. Currently we always try to put object to blobstor if putting to write cache fails.
Describe the solution you'd like
Don't do that in case write cache is full. If that's the case it's supposed to be flushing to blobstor at the maximum speed possible and additional threads pushing objects to blobstor directly can only slow it down. If it's full because it can't flush objects to blobstor trying this direct put doesn't help either.
Describe alternatives you've considered
Keep things as is. Current behavior is somewhat better for the case when write cache can't put objects to blobstor, but direct put somehow can. I don't see this happening, but who knows.
Additional context
Metadata
Metadata
Assignees
Labels
I4No visible changesNo visible changesS3Minimally significantMinimally significantU4Nothing urgentNothing urgentenhancementImproving existing functionalityImproving existing functionalityneofs-storageStorage node application issuesStorage node application issuesperformanceMore of something per secondMore of something per second