samg / timetrap

Simple command line timetracker
http://rubygems.org/gems/timetrap
Other
1.48k stars 115 forks source link

timetrap archive to separate DB #162

Open jostber opened 6 years ago

jostber commented 6 years ago

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?

samg commented 6 years ago

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.

jostber commented 6 years ago

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?

samg commented 6 years ago

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.