killed by oomkiller on large location-history

[khimaros]

memory seems to grow unbounded and is oom-killed after about 20GB memory usage.

this is happening while loading a ~1GB uncompressed location history.

[simonw]

The memory profiler tricks I used in dogsheep/healthkit-to-sqlite#7 could help figure out what's going on here.

[khimaros]

it looks like almost all of the memory consumption is coming from json.load().

another direction here may be to use the new "Semantic Location History" data which is already broken down by year and month.

it also provides much more interesting data, such as estimated address, form of travel, etc.