@Bryan_Leavelle The telemetry system is what comes before the database; it’s a messaging framework to transmit statistics from point A to B during runtime. The database is one of many such B points. Monty uses Wandb for its database needs, which is specifically tailored to AI training. Personally, I’m not sure what tangible additional benefits would a bespoke SQL database provide, at least at this stage.
this is very funny now after looking at it. this is the database manager in me wishing everyone’s results were instantly available to everyone else using the system, that’s all. shared results is what it gets ya, with fast queries 
Results being instantly available is one of the core goals of telemetry 
. At present, the data accumulates in place, and is then collected at specific boundaries (e.g. after each episode) by logger classes, who then forward aggregated data to the database and/or visualizations. We’re trying to make data reporting more proactive by having a telemetry framework to emit data live at the point of origin. This is primarily to facilitate creating visualizations (see 2026/07 - Upcoming and Ongoing Engineering Platform Changes, Tristan showed a nice demo). It also enables more fine-grained database logging too, so it’s not unlikely that the database portion might get some overhauls later down the road.
2 Likes
ok. that is awesome. thank you!