They could have been more intensive indeed, but perhaps with the old implementation. I don't see why a single store query would consume more resources than Filter connection with 3 remote peers. I'd give it a try, anyway it should only kick in when a connection is lost, not constantly syncing.
Originally posted by @igor-sirotin in status-im/status-go#7673 (comment)
we decided to pause store queries in the BG because they are more intensive, so we wanted to avoid using too much memory while the phone is backgrounded. If it uses too much, the Android system could decide to kill it.
However, now, we have made a lot of improvements, so doing them might be ok.
They could have been more intensive indeed, but perhaps with the old implementation. I don't see why a single store query would consume more resources than
Filterconnection with 3 remote peers. I'd give it a try, anyway it should only kick in when a connection is lost, not constantly syncing.Originally posted by @igor-sirotin in status-im/status-go#7673 (comment)
we decided to pause store queries in the BG because they are more intensive, so we wanted to avoid using too much memory while the phone is backgrounded. If it uses too much, the Android system could decide to kill it.
However, now, we have made a lot of improvements, so doing them might be ok.