giterest

hi there, e.g. the oldest files at /HealthData/FitFiles/Monitoring/2016 have a last change timestamp of 23rd may 2021, 11:43 (CEST). the last time i ran make was today around 07:00 (CEST)...

hi. started another try (first one since my last post, so more than 2 days). as soon as [make] hits "___Analyzing Data___" it starts from the very beginning (2016...) and...

weird.. i run garmindb on a debian buster VM with 4 cpus and 8gig of ram. i use that VM solely for testing, so there's nothing else running on it.

thanks for the tip, reinstalled sqlite3 package on test-VM and also installed GarminDB on my PROD machine - same behaviour. i also checked sysload during the analysis, there's no significant...

profiling runs.. will come back asap as i have some results to share. update - the analyzing was quite fast as you can see ~11mins, compared to running make. i'll...

hi all, so it seems that on TEST the sqlite-DB got somehow corrupted, causing garmindb to have that immense I/O times. anyhow, on PROD it runs fine (~12-15mins), after copying...