[#23] Client: Refactoring to optimize memory usage #28

Merged
PavelGrossSpb merged 2 commits from PavelGrossSpb/frostfs-sdk-csharp:misc/refactoring into master 2024-09-12 12:54:25 +00:00
Member

Signed-off-by: Pavel Gross p.gross@yando.com

Signed-off-by: Pavel Gross <p.gross@yando.com>
PavelGrossSpb added 1 commit 2024-09-11 07:59:45 +00:00
[#23] Client: Refactoring to optimize memory usage
All checks were successful
DCO / DCO (pull_request) Successful in 33s
6562aa27a5
Signed-off-by: Pavel Gross <p.gross@yando.com>
PavelGrossSpb requested review from orikik 2024-09-11 08:01:09 +00:00
PavelGrossSpb requested review from dstepanov-yadro 2024-09-11 08:02:14 +00:00

What optimizations are added in this PR? I see 141 changes in one commit, with most of the changes being name changes.

What optimizations are added in this PR? I see 141 changes in one commit, with most of the changes being name changes.
dstepanov-yadro reviewed 2024-09-11 09:03:24 +00:00
@ -0,0 +1,10 @@
namespace FrostFS.SDK;
public enum FrostFsObjectMatchType

Why this change? Full type name was FrostFS.SDK.ObjectMatchType, but now it is FrostFS.SDK.FrostFsObjectMatchType. Does FrostFS.SDK namespace has other ObjectMatchType except FrostFs one?

Why this change? Full type name was `FrostFS.SDK.ObjectMatchType`, but now it is `FrostFS.SDK.FrostFsObjectMatchType`. Does `FrostFS.SDK` namespace has other `ObjectMatchType` except `FrostFs` one?
Author
Member

Fixed to FrostFsMatchType. We have MatchType from GRPC namespaces. All users types starts with FrostFs to avoid full naming.

Fixed to FrostFsMatchType. We have MatchType from GRPC namespaces. All users types starts with FrostFs to avoid full naming.
dstepanov-yadro marked this conversation as resolved
@ -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.

As far as I remember, C# code style requires that namespace must correspond directory structure.
Author
Member

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?

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

No
dstepanov-yadro marked this conversation as resolved
PavelGrossSpb added 1 commit 2024-09-12 08:56:43 +00:00
[#23] Client: Refactoring to optimize memory usage
All checks were successful
DCO / DCO (pull_request) Successful in 53s
704ce41173
Signed-off-by: Pavel Gross <p.gross@yando.com>
Author
Member

The main optimization is creating GRPC object once. In case of multiple usage, only one coventation is applied.

The main optimization is creating GRPC object once. In case of multiple usage, only one coventation is applied.
orikik approved these changes 2024-09-12 11:53:29 +00:00
PavelGrossSpb merged commit 704ce41173 into master 2024-09-12 12:54:25 +00:00
PavelGrossSpb deleted branch misc/refactoring 2024-09-12 12:54:25 +00:00
Sign in to join this conversation.
No description provided.