[#23] Client: Refactoring to optimize memory usage #28
No reviewers
Labels
No labels
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-sdk-csharp#28
Loading…
Reference in a new issue
No description provided.
Delete branch "PavelGrossSpb/frostfs-sdk-csharp:misc/refactoring"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Signed-off-by: Pavel Gross p.gross@yando.com
What optimizations are added in this PR? I see 141 changes in one commit, with most of the changes being name changes.
@ -0,0 +1,10 @@
namespace FrostFS.SDK;
public enum FrostFsObjectMatchType
Why this change? Full type name was
FrostFS.SDK.ObjectMatchType
, but now it isFrostFS.SDK.FrostFsObjectMatchType
. DoesFrostFS.SDK
namespace has otherObjectMatchType
exceptFrostFs
one?Fixed to FrostFsMatchType. We have MatchType from GRPC namespaces. All users types starts with FrostFs to avoid full naming.
@ -1,13 +1,11 @@
using FrostFS.SDK.ModelsV2;
namespace FrostFS.SDK.ClientV2;
As far as I remember, C# code style requires that namespace must correspond directory structure.
Yes, it one of the suggestion. Requirements are defined by vendor. As for me, folder hierarchy is useful for structuring, but dozens of using - are not, especially for external users. Do we have such a requirement?
No
The main optimization is creating GRPC object once. In case of multiple usage, only one coventation is applied.