WIP: Cache head results in the request context #974

Closed

fyrchik wants to merge 6 commits from fyrchik/frostfs-node:head-cache into master

fyrchik commented

2024-02-09 14:14:53 +00:00

Owner

No description provided.

fyrchik added 6 commits 2024-02-09 14:14:55 +00:00

aclsvc: Do not use functional options in NewMessageHeaderSource() 08c6578156

There is only 1 option, which is provided on every callsite.

Signed-off-by: Evgenii Stratonikov <e.stratonikov@yadro.com>

objectsvc: Make requestContextKey private 2d3bed89d2

1. Disallow storing wrongly typed value by this key.
2. This is the way described in context.Value() documentation.

Signed-off-by: Evgenii Stratonikov <e.stratonikov@yadro.com>

aclsvc/v2: Allocate RequestContext once d9ab944c22

Signed-off-by: Evgenii Stratonikov <e.stratonikov@yadro.com>

aclsvc/v2: Add toRequestContext() helper fb37fbf1d6

Signed-off-by: Evgenii Stratonikov <e.stratonikov@yadro.com>

aclsvc: Provide context to CheckEACL 5b0b70b6ac

Remove context.TODO() and allow passing RequestContext struct later.

Signed-off-by: Evgenii Stratonikov <e.stratonikov@yadro.com>

DCO action / DCO (pull_request) Failing after 2m5s

Details

Vulncheck / Vulncheck (pull_request) Successful in 2m3s

Details

Build / Build Components (1.21) (pull_request) Successful in 4m38s

Details

Build / Build Components (1.20) (pull_request) Successful in 4m52s

Details

Tests and linters / Staticcheck (pull_request) Successful in 6m17s

Details

Tests and linters / Lint (pull_request) Successful in 7m26s

Details

Tests and linters / Tests (1.20) (pull_request) Successful in 8m10s

Details

Tests and linters / Tests (1.21) (pull_request) Successful in 8m19s

Details

Tests and linters / Tests with -race (pull_request) Successful in 8m41s

Details

f3bd92aeda

Signed-off-by: Evgenii Stratonikov <e.stratonikov@yadro.com>

fyrchik commented

2024-02-28 19:09:13 +00:00

Author

Owner

I was convinced this is not the best way to do it.
We will revisit this if we need perfomance improvements in v0.38
If not, a better implementation will follow.

I was convinced this is not the best way to do it. We will revisit this if we need perfomance improvements in v0.38 If not, a better implementation will follow.