Peter Storch

The deletion count could be a solution. Regarding the space: according to SQLite the free space in the db file is not lost. SQLite will reuse it to store new...

How do we want to implement the deletion count? - remove the auto-vacuum on delete - count all deletes - check on startup of OT if "threshold" is reached and...

Makes sense. What is a reasonable threshold? 100 deleted tracks?

So we need to count the deleted TrackPoints not Tracks?

I just tried it `select changes()` returns the same number as the return value of the `delete` statement itself, only the number of track rows deleted. The documentation says ```...

Observation: my 13km Tracks have around 2300 Trackpoints. So a threshold of 10k is triggering the vacuum latest after 5 tracks deleted.

@Saboe thanks for your tests > Because there isn't any visual thing that shows the user that something is ongoing. OT shows a notification as long as the deletion is...

Maybe trimming function by time (remove 30 seconds from the start and 35 minutes from the end)?

While testing the current export function I recognized that, when using a cloud destination, hundreds of small files take longer to upload than one single big file. So I think...

This gets more and more rediculous.