I have the impression (but I’ll let you confirm) that the analysis runs locally on our phones. Maybe also on the website when you’re looking for a big screen.
You’ve really improved the analyzer ( ). Today, in my notebook, I have traces signed from V8 to V15.
Would it be possible to do batch processing to update everything with the latest analyzer?
The batch could even potentially be a standalone program?
There’s no urgency to my request… just intellectual curiosity
The analysis runs on our servers, not locally on the device—the app sends the raw GPS data and receives the results in return.
I’ve thought about batch reprocessing with the latest analyzer, but there are a few reasons it doesn’t exist yet: it’s resource-intensive, and more importantly, it would change users’ statistics without them knowing why. If your numbers change without any explanation, it’s confusing. The current approach—manual, session-by-session reprocessing—means that the user who triggers it understands why their stats have changed.
That said, I want to build this properly at some point, with a clear interface that explains what will happen before any reprocessing takes place. I can’t give a timeline yet; I still need to think through the best implementation.
If you’d like to see this feature prioritized, feel free to vote in this thread—it helps me gauge demand.
I understand the server load (in a previous life, a very long time ago, I was an IT professional ).
I’m actually surprised by the excellent response times despite the centralized processing (which is why I asked the question in the first place). I’ve seen other applications take forever to serve up session stats because they’re victims of their own success when it comes to server capacity—and the costs that entails.
No, I really don’t need it to be prioritized.
However, there’s one point I wasn’t clear about: the idea was for the user to request batch processing of all their sessions. That way, they know why their stats are going to change, since they’re the one requesting the processing by clicking an option in a menu.
To keep things running smoothly on the server, this batch could try to perform the recalculation asynchronously, at low priority, and send a notification once the task is complete.
These are just ideas I’m sharing with you (although I’m sure you already have plenty of ideas for improving your baby ).
Please don’t feel any pressure regarding any improvement ideas I might send your way. I’m already completely satisfied with how WST currently works
