performance regression

[gour]

Hello,

I've posted timings in the 0.0.9 to #24 - it seems there is performance regression?

[dagraham]

I'm working on performance but, meanwhile, an idea occurred to me. tklr now supports an "auto save" feature. Basically it means that you can enter a "current_command" in config.toml, e.g.,

# current_command: optional CLI snippet to run after saving changes in the UI.
# Example: 'days --end 8 --width 46'
# Prefix with '!' to run a standalone command/script (no automatic 'tklr').
current_command = "!/Users/dag/.local/bin/write_current.sh"

And then when a record in the database changes or a new day begins, the named script will be executed. Here's my "write_current.sh":

#!/bin/zsh

AGENDA=~/tklr/agenda.txt
DAYS=~/tklr/days.txt
WEEKS=~/tklr/weeks.txt
date > "$AGENDA"
echo >> "$AGENDA"
tklr --home ~/tklr agenda --width 46 >> "$AGENDA"
date > "$DAYS"
echo >> "$DAYS"
tklr --home ~/tklr days --width 46 >> "$DAYS"
date > "$WEEKS"
echo >> "$WEEKS"
tklr --home ~/tklr weeks --width 46 >> "$WEEKS"

With this setup, I always have a current version of agenda, days and weeks in agenda.txt, days.txt and weeks.txt, respectively. In my case these files are actually symbolic links to similarly named files in by Google Drive so that I can view them using my iPhone.

With a similar setup you could use, e.g.,

cat <path to your days.txt> 

as an alternative to using tklr --home ... days. Here are my times using cat:

% /usr/bin/time -p cat ~/tklr/days.txt                                           ⏱ 7:36:17
Wed Jan  7 06:15:01 EST 2026

 Wed, Jan 7, 2026 (today)
  * 9-10am pest control

 Thu, Jan 8, 2026
  * 8-9:30am pickleball

 Sat, Jan 10, 2026
  * 6-9pm Cassel's for dinner

 Mon, Jan 12, 2026
  ~ 8am trash to curb
  * 8-9:30am pickleball
  * 3-4pm Sonia - cleaners
real 0.00
user 0.00
sys 0.00

That should be fast enough to satisfy even you. 😊

[gour]

real 0.00
user 0.00
sys 0.00

That should be fast enough to satisfy even you. 😊

I'd not complain. 😉

[gour]

I'm working on performance but, meanwhile, an idea occurred to me. tklr now supports an "auto save" feature. Basically it means that you can enter a "current_command" in config.toml, e.g.,

# current_command: optional CLI snippet to run after saving changes in the UI.
# Example: 'days --end 8 --width 46'
# Prefix with '!' to run a standalone command/script (no automatic 'tklr').
current_command = "!/Users/dag/.local/bin/write_current.sh"

And then when a record in the database changes or a new day begins, the named script will be executed. Here's my "write_current.sh":

Very clever idea!!

That should be fast enough to satisfy even you. 😊

I can confirm the same timing. 😉

[dagraham]

Some performance tweaks for 0.0.10 just released. My times:

~/Projects/tklr-uv
% /usr/bin/time -p tklr --home examples/ days > /dev/null                                      ⏱ 21:27:23
real 0.50
user 0.41
sys 0.07
~/Projects/tklr-uv
% /usr/bin/time -p tklr --home examples/ weeks > /dev/null                                     ⏱ 21:28:07
real 0.55
user 0.46
sys 0.08
~/Projects/tklr-uv
% /usr/bin/time -p tklr --home examples/ agenda > /dev/null                                    ⏱ 21:28:17
real 0.51
user 0.42
sys 0.07

[dagraham]

New implementation of save_after automatically writes to "current.txt" in the active tklr home directory. My config.toml setting:

# current_command: optional CLI snippet to run after saving changes in the UI.
# Example: 'days --end 8 --width 46'
# Prefix with '!' to run a standalone command/script (no automatic 'tklr').
# The output of this command will be written to "current.txt" in the Tklr home
# directory.
current_command = "!/opt/homebrew/bin/timeout 10 /Users/dag/.local/bin/write_current.sh"

The homebrew timeout entry gives the command 10 seconds to complete and then closes it - probably overkill.

My write_current.sh:

#!/bin/zsh

date "+Agenda: %Y-%m-%d %H:%M:%S"
echo
tklr --home ~/tklr agenda --width 46