Hmmm....All of the database writes appear to be wrapped in transactions and if there were any missing transactions, GSAK should be throwing the transaction warning, which it isn't. I'm at a loss to explain the difference you're seeing and attributing to GSAK Build 35.
Please elaborate on the testing protocol you used to determine the speed difference. To have an accurate test, you would need to use the exact same data with both versions of GSAK, i.e.:
1) Revert GSAK to Build 34
2) Take a backup of your database
3) Run the Five New Logs macro
4) Load GPX File(s)
5) Run the Five New Logs macro and time the results.
6) Restore the backup of your database from step 2 (so that the original data is in place).
7) Run the Five New Logs macro
8) Load the same GPX file(s) as you loaded in step 4
9) Run the Five New Logs macro and time the results.
Is that what you did?
Please elaborate on the testing protocol you used to determine the speed difference. To have an accurate test, you would need to use the exact same data with both versions of GSAK, i.e.:
1) Revert GSAK to Build 34
2) Take a backup of your database
3) Run the Five New Logs macro
4) Load GPX File(s)
5) Run the Five New Logs macro and time the results.
6) Restore the backup of your database from step 2 (so that the original data is in place).
7) Run the Five New Logs macro
8) Load the same GPX file(s) as you loaded in step 4
9) Run the Five New Logs macro and time the results.
Is that what you did?
