search

stevenocchipinti / poosnooker

0 stars 0 forks source link

Burning through free quota?! #15

Closed stevenocchipinti closed 6 years ago

stevenocchipinti commented 6 years ago

It seems that in development, I tend to be going through the free plan quota fairly quickly!

The data is available through the console and at this URL: https://console.cloud.google.com/appengine/quotadetails?project=poo-snooker&authuser=0

I'm currently not sure what counts as a "read operation" but because each time any action happens in this app it will write a new record, even if just cycling through the players, this will generate more traffic that otherwise.

Given the free quota allows 50,000 reads and 20,000 writes, but its the reads that I'm burning through. One theory is that for every write I do, maybe I am reading all events instead of just the ones that have been added but this needs to be investigated.

stevenocchipinti commented 6 years ago

Sounds like I need to use the "cursor" feature mentioned in the "Managing large result sets" section of this document: https://firebase.google.com/docs/firestore/pricing#operations

This could be done with startAfter as documented here: https://firebase.google.com/docs/firestore/query-data/query-cursors

stevenocchipinti commented 6 years ago

Although, because the listener is only setup once upon construction, that listener would need to be detached and then reattached with a startAfter configured :/