morph: Fix batch size in TraverseIterator() #1000
No reviewers
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#1000
Loading…
Reference in a new issue
No description provided.
Delete branch "fyrchik/frostfs-node:fix-iterator"
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?
Initial prefetch size can be arbitrary an restricted only by VM/RPC
limits. For TraverseIterator() there is an explicit check on the
server-side, though.
Introduced in
df055fead5
.Refs #931.
We can increase neo-go setting, but for public component we better use defaults.
00a1a8da56/pkg/services/rpcsrv/server.go (L2533C29-L2533C30)
Testing done:
41647b6ac5
to175b625400
175b625400
to628803761a
WIP: morph: Fix batch size in TraverseIterator()to morph: Fix batch size in TraverseIterator()After https://github.com/nspcc-dev/neo-go/issues/3276 we might do better.
@ -260,8 +260,13 @@ func (c *Client) TestInvokeIterator(cb func(stackitem.Item) error, batchSize int
_ = c.rpcActor.TerminateSession(sid)
}()
// Batch size for TraverseIterator() it restricted on the neo-go size.
shouldn't it be
is restricted by
?Thanks, it is actually
restricted on the neo-go siDe
628803761a
to54caf1bde8