#dagql cache?
1 messages · Page 1 of 1 (latest)
Dagql does cache queries already, but only within a single session. Caching results in sqlite instead would definitely be a fun experiment. I'm also really feeling the pain of not having caching for module functions across sessions. Nearly all of mine are cacheable but they re-run every time. 😦
Definitely need to measure first though to see where time is being spent, could be any number of things. Do you have a slow example I can check out?
dagger -m github.com/shykes/daggerverse/dagger call engine versions
dagger -m github.com/shykes/daggerverse/daggy call container terminal
for me this only seems to be slow because it walks through a list of 100 items and makes an API call for each, the module init part is pretty fast (1-2 seconds). probably a good example where a query builder would help. but that will also be expensive because each tag.name selection is still going to need a call to the Supergit module. (This also surfaced some small TUI bugs though, so yay)
this one is also pretty fast for me, module initialization wise: https://asciinema.org/a/B5KeP9coj3SkTdDorAYFsM1B9
yeah that one was not the best illustration of slow module load