Aleksey Savchuk a-savchuk
  • i guess we doin blockchain now

  • Joined on 2024-07-02
a-savchuk commented on issue TrueCloudLab/frostfs-node#1448 2024-11-05 14:49:08 +00:00
not enough nodes to SELECT from answer on the dev-env

In general, that error could occur not only on the 1st epoch but also when a network map has had not enough nodes on the previous two epochs (fact checking needed)

https://git.frostfs.info/Tru

a-savchuk commented on issue TrueCloudLab/frostfs-node#1450 2024-11-05 08:41:31 +00:00
Measure tombstone placement duration depending on tombstone size

@a-savchuk Could you share benchmark setup and code?

I added them in the first comment

a-savchuk commented on issue TrueCloudLab/frostfs-node#1450 2024-11-05 06:56:20 +00:00
Measure tombstone placement duration depending on tombstone size

I collected an off-CPU profile as I was advised by @dstepanov-yadro *thanks*. Here's what I found

Off-CPU profile (for 10.000 parts only)

Data: [off_cpu_10000_parts.pb.gz](/attachments/68…

a-savchuk deleted branch doc-max-object-size from a-savchuk/frostfs-api 2024-11-02 13:45:28 +00:00
a-savchuk commented on issue TrueCloudLab/frostfs-node#1450 2024-11-02 12:20:03 +00:00
Measure tombstone placement duration depending on tombstone size

I've decided to write a benchmark for the (*StorageEngine).Inhume method. I ran it for 1, 10, 100, 1.000, and 10.000 addresses in a tombstone, and I collected a CPU profile and memory profile…

a-savchuk pushed to benchmark-inhume-multipart at a-savchuk/frostfs-node 2024-11-02 11:11:20 +00:00
87e909343f [#1450] engine: Add benchmark Inhume when there's many addresses
a-savchuk created branch benchmark-inhume-multipart in a-savchuk/frostfs-node 2024-11-02 09:55:22 +00:00
a-savchuk pushed to benchmark-inhume-multipart at a-savchuk/frostfs-node 2024-11-02 09:55:22 +00:00
0eac5c66de [#1450] engine: Add benchmark Inhume when there's many addresses
a8b18317c1 [#1450] engine/test: Refactor (*testEngineWrapper).setInitializedShards
Compare 2 commits »
a-savchuk pushed to master at a-savchuk/frostfs-node 2024-11-02 09:42:49 +00:00
d19ab43500 [#1462] node: Add off-cpu profiler
5bcf81d1cc [#1466] Remove woodpecker CI
c2effcc61c [#1465] Makefile: Update golangci-lint, fix warnings
2285cfc36f [#1464] frostfsid: Cache subject not found error
e74d05c03f [#1464] frostfsid: Add cache metrics
Compare 50 commits »
a-savchuk approved TrueCloudLab/frostfs-dev-env#88 2024-10-31 07:36:52 +00:00
Remove nats service
a-savchuk approved TrueCloudLab/frostfs-node#1466 2024-10-31 07:14:21 +00:00
Remove woodpecker CI
a-savchuk deleted branch container-get-on-first-epoch from a-savchuk/frostfs-node 2024-10-30 11:10:57 +00:00
a-savchuk pushed to container-get-on-first-epoch at a-savchuk/frostfs-node 2024-10-30 09:52:12 +00:00
d28a5d2d7a [#1448] container/ape: Ignore an error when getting a role
87ac3c5279 [#1458] object: Make patch not set key before target construction
d5ee6d3039 [#1456] morph: Use DialerSource interface instead of internal struct
Compare 3 commits »
a-savchuk commented on pull request TrueCloudLab/frostfs-node#1454 2024-10-30 09:49:40 +00:00
container/ape: Ignore an error when getting a role

Yeah, removed it

a-savchuk pushed to container-get-on-first-epoch at a-savchuk/frostfs-node 2024-10-30 09:48:47 +00:00
6daa1fda7f [#1448] container/ape: Ignore an error when getting a role
a-savchuk commented on pull request TrueCloudLab/frostfs-node#1454 2024-10-30 09:43:34 +00:00
container/ape: Ignore an error when getting a role

Made the PR description more detailed:

The affected function isContainerNode is used for determining if an actor is a container role when checking an APE rule. It's guaranteed that the policy…

a-savchuk pushed to container-get-on-first-epoch at a-savchuk/frostfs-node 2024-10-29 14:36:01 +00:00
e70c2cedbe [#1448] container/ape: Ignore an error when getting a role
433aab12bb [#1455] cli: Handle missing home directory
Compare 2 commits »
a-savchuk commented on issue TrueCloudLab/frostfs-node#1448 2024-10-29 13:15:32 +00:00
not enough nodes to SELECT from answer on the dev-env

I noticed that the problem occurs only when the -g flag is used