Skip to content

qml: improve UI responsiveness during sync - #10750

Open
f321x wants to merge 6 commits into
spesmilo:masterfrom
f321x:qml_history_txid_map
Open

qml: improve UI responsiveness during sync#10750
f321x wants to merge 6 commits into
spesmilo:masterfrom
f321x:qml_history_txid_map

Conversation

@f321x

@f321x f321x commented Jul 13, 2026

Copy link
Copy Markdown
Member

I wanted to sync a watch only wallet with this large history address "1K6KoYC69NnafWJ7YgtrpwJxBLiijWqwa6" on Android which was so slow the app became unresponsive after some minutes during the sync.
These commits resolve several inefficiencies and the UI stays fully responsive and manages to finish the sync.

f321x added 6 commits July 13, 2026 14:01
Add a txid -> model row index dict to `QETransactionListModel`
instead of re-iterating the `tx_history` list on each event
to find the tx item.
This noticeably unblocks the UI during sync of a large wallet.
During synchronization, new_transaction fires for every incoming tx and
each balanceChanged emit makes QML recompute the balance on the GUI
thread. The balance isn't shown anyway during sync.
The addressCoinModel property getter lazily constructs
QEAddressCoinListModel, whose __init__ runs a full (slow) initModel().
Instead of initializing it on a new transaction, blocking the UI,
just initialize it lazily when the user actually opens it.
Same pattern as importAddresses/importPrivateKeys.
Change per-tx event callback logs to debug, might make the process
a bit less clogged if there are many txs.
Don't compute the wallet balance delta for the new tx notification
shown after synchronizing the wallet if the notification batch
exceeds 10 txs. Otherwise the calculation will block the UI, especially
for large wallets with many new txs after initial sync.
emit a single dataChanged signal over the whole model index range
once in `QETransactionListModel.updateBlockchainHeight()` instead
of emitting a separate signal for each transaction.
@f321x f321x added the gui-qml label Jul 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant