Using Firestore on a watch consumes a lot of power. Is there an optimization solution?

[NeilYu6]

use addSnapshotListener

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[MarkDuckworth]

@zhanlv, there are no optimizations that I'm aware of. You could see if poling the backend using getDocs() uses less power, but this has other tradeoffs.

Can you please explain the first screenshot? What in that screenshot it indicating that a watch uses lots of power?

[NeilYu6]

@zhanlv, there are no optimizations that I'm aware of. You could see if poling the backend using getDocs() uses less power, but this has other tradeoffs.

Can you please explain the first screenshot? What in that screenshot it indicating that a watch uses lots of power?

@MarkDuckworth

[MarkDuckworth]

@zhanlv, a few things.

1. A watch requires an open connection with the server, even if data is not actively sent. You could play with polling using getDocs() or potentially disable the network during certain times using disableNetwork(). But those may affect the viability of your solution.
2. We can't move forward with the screenshot of steady current. It's not specific enough to indicate any issue with Firestore. If you believe there is an issue here, perhaps it would be better to profile your application and show that Firestore is indeed consuming significant CPU on your machine.

[google-oss-bot]

Hey @zhanlv. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[google-oss-bot]

Since there haven't been any recent updates here, I am going to close this issue.

@zhanlv if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.