Things in the data subteam codebase are currently mostly implemented with no optimizations. For better performance and memory usage, a variety of things can be done:
Data accessed through the TelemetryData class could be cached in some way, although it might make more sense for the caching to happen in a different part of the codebase.
Beyond just getting one "row"/"column" at a time from a TelemetryData object, perhaps there should be ways of getting even more data at once.
It might be possible to optimize some queries to the database, especially in light of the above points.
Things in the data subteam codebase are currently mostly implemented with no optimizations. For better performance and memory usage, a variety of things can be done:
TelemetryDataclass could be cached in some way, although it might make more sense for the caching to happen in a different part of the codebase.TelemetryDataobject, perhaps there should be ways of getting even more data at once.