I’ve been testing the Unity SDK for Firebase Realtime Database, and see that when actively reading data from listeners, each read of ~20 bytes incurs a “billable size” of 4-5kb.
The docs point to overhead for setting up the connection, but these reads are all on the same connection. I asked support, and they suggested that in their test, their overhead is 10-15kb per call.
I was expecting the documented 3kb for the connection setup, and minimal per call after that.
Is it really expected behavior that every consecutive read has an extra 5-10kb overhead for the billable size?
Ryan Feldman is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.