Target version set to 3.0
----------------------------------------
Feature #106: JSON format ride files
http://bugs.goldencheetah.org/issues/106
Author: Mark Liversedge
Status: Resolved
Priority: Normal
Assigned to: Mark Liversedge
Category:
Target version: 3.0
Patch Attached: Yes
The gc xml format can be slow to parse, especially for longer rides, JSON provides similar human-readable and machine-interpretable files but are much simpler to parse, leading to performance gains.
The attached patch introduces a reader/writer for JSON format and initial tests indicate that writing is 10x faster, whilst reading is 4x faster.
It is worth noting that the computation of ride metrics when a file is first opened is one of the main reasons for the delay between selecting a ride and the display being updated, this can only get worse over time as more metrics are introduced. We may wish to consider writing pre-computed metrics to the ride file to avoid this step (I have coded this up separately and it makes a SIGNIFICANT improvement to ride list navigation).
Attached patch requires flex/bison, but these are pretty standard tools.
--
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.goldencheetah.org/my/account
Status changed from Resolved to Closed
Implemented in V3 as part of the initial branch creation and has been subject to fairly significant testing.
----------------------------------------
Feature #106: JSON format ride files
http://bugs.goldencheetah.org/issues/106
Author: Mark Liversedge
Status: Closed