🎁 [Feature Request]: Fetch price tables in batches

[ozgunozerk]

What is the feature you would like to see?

1. after a long time, say 3 years that a client was offline, or a user switched to a new device
2. then the client requested all price tables for the last 3 years
3. it might be 100-200 MB of data to send in a single request. This is too much
4. the good news is, we don’t have to worry about that for now

At some time in the future, the client should fetch price tables in batches, divided into a few requests.

[ozgunozerk]

Calculation:

• 1 year, 4 snapshots per day -> 365 x 4 price tables
• 4 maps in each price table (32 byte per map) -> 4 x 32 = 128 overhead per each price table
• each entry in map -> 8 byte for integer (value), on average 6 characters for string (key) -> 8 + 6 + 1 (for strings, we put an extra byte) = 15 byte per entry
• 104 entry for nasdaq , 50 entry for bist, 31 entry for forex, 100 entry for crypto -> 104 + 50 + 31 + 100 = 285 entries

365 x 4 x (32 + 285 x 15) = 6288220 bytes -> ~6.28 megabytes.

Say, for 10 years worth of price tables, it will require to fetch ~63 megabytes at once, which could be problematic

[ozgunozerk]

here is the documentation for calculation sizes for firebase documents: https://firebase.google.com/docs/firestore/storage-size#document-size