Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UTXO's response time problem #300

Open
TurgutKanceltik opened this issue Dec 26, 2020 · 7 comments
Open

UTXO's response time problem #300

TurgutKanceltik opened this issue Dec 26, 2020 · 7 comments

Comments

@TurgutKanceltik
Copy link

Hi every body,

First of all our NBXplorer includes BTC, LTC and DASH. In the early days, when bringing in UTXOs, the response time was pretty short, like 1-2 seconds. But then, as the number of UTXO increased, the response times increased. At first, we got an answer in 40-50 seconds, then it extended up to 2-3 minutes. After that, we applied prune for all strategies and then restarted NBXplorer. This time around, response time has decreased from 2-3 minutes to 30-40 seconds. However, I still think that is a problem because I'm talking about the UTXO number of over 1300-1400. The majority of these UTXOs are very small amounts that we cannot spend. Why can't we spend it because if we spend those small amounts, the transaction size will be huge and the commission amount will be large accordingly.

@NicolasDorier
Copy link
Member

NicolasDorier commented Dec 29, 2020

@TurgutKanceltik 1300/1400 UTXO is not a lot, the time it takes is caused by the number of transactions required to build a wallet's UTXO set. Pruning remove the transactions which are not affecting the current UTXO set anymore.

  1. Do you run latest version of NBX?
  2. Why not consolidating those small utxos in a single transaction and pay just 1sat/b ?

@TurgutKanceltik
Copy link
Author

We updated to the latest. However, nothing has changed much, the response still comes in a very long time. Do we really need consolidating those small utxos in a single transaction and pay just 1sat / b? I think we shouldn't need this for this much UTXO.

@NicolasDorier
Copy link
Member

@TurgutKanceltik have you tried to modify the --dbcache parameter? So NBXplorer is trying to keep more data in RAM, this may improve performance?

@TurgutKanceltik
Copy link
Author

@NicolasDorier Yes we are using it for a long time as --dbcache 500 but still slow. How do you suggest editing it?

@NicolasDorier
Copy link
Member

@TurgutKanceltik I think 500 should be plenty enough.
Yeah, I would advise you to spend those small utxo and then prune when it has a bunch of confirmation.
More than 1sat/bytes, as these days the mempool is full.

@TurgutKanceltik
Copy link
Author

@NicolasDorier Of course, this is not a problem for me. I can spend small UTXOs. However, I wonder is this a bug? Because the response time is very abnormal for so few UTXO.

@NicolasDorier
Copy link
Member

NicolasDorier commented Jan 7, 2021

I will try to see if I can reproduce. This is indeed strange, though the time it takes is proportional to the number of transactions impacting the UTXO set of the wallet rather than the number of UTXO.
I would not expect anything less than 50K transaction to be a problem though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants