z_listreceivedaddress with no filters is very slow #353

Closed
opened 6 months ago by duke · 1 comments
duke commented 6 months ago
Owner

z_listreceivedaddress RPC is really meant to be used with various optional "filter" arguments that don't exist in z_listreceivedbyaddress . But if no filters are used and it's called in the simplest way hush-cli z_listreceivedaddress zaddr then it's drastically slower than hush-cli z_listreceivedbyaddress zaddr . This should probably be in the RPC help, something like "Note that this RPC is much slower than z_listreceivedbyaddress if no filters are used. You should use that RPC if you don't need any filters."

For example, on one particular large wallet, z_listreceivedbyaddress takes 4.6s to return data while z_listreceivedaddress takes 1 minute and 53s to return data.

z_listreceivedaddress RPC is really meant to be used with various optional "filter" arguments that don't exist in z_listreceivedbyaddress . But if no filters are used and it's called in the simplest way `hush-cli z_listreceivedaddress zaddr` then it's drastically slower than `hush-cli z_listreceivedbyaddress zaddr` . This should probably be in the RPC help, something like "Note that this RPC is much slower than z_listreceivedbyaddress if no filters are used. You should use that RPC if you don't need any filters." For example, on one particular large wallet, `z_listreceivedbyaddress` takes 4.6s to return data while `z_listreceivedaddress` takes 1 minute and 53s to return data.
duke added the
documentation
label 6 months ago
Poster
Owner

RPC help updated on dev, closing

RPC help updated on `dev`, closing
duke closed this issue 6 months ago
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.