timetrap icon indicating copy to clipboard operation
timetrap copied to clipboard

Published 20 hours ago • verified publisher icon samg

timetrap archive to separate DB

Open jostber opened this issue 7 years ago • 3 comments

My timetrap DB is getting quite large with many thousand entries and it has gotten much slower lately. Is there a way to move the archived entries to another DB or another way make it faster again?

jostber avatar Aug 16 '17 11:08 jostber

One solution would be to move the current SQLite database to a new location. Timetrap will automatically create a new one the next time you run it. If you want to view the archived entries you could temporarily configure timetrap to point back at the old db via the timetrap.yml config. Let me know if that solves your problem.

samg avatar Sep 13 '17 04:09 samg

I can try that. Actually running timetrap in Linux is very snappy with a few seconds response, while running it in Cygwin on Windows has become very slow with over 30 seconds to wait before anything happens. Is there anything that can be done to speed it up in Cygwin?

jostber avatar Sep 19 '17 19:09 jostber

I'm not sure, and am only lightly familiar with Cygwin. It might be possible for you to profile timetrap to get more details into where the time is going.

samg avatar Sep 20 '17 04:09 samg