Track compute time in cache metadata

[dbeach24]

Keep track of compute time in the cache metadata

[riedel]

Somehow we missed this PR 4 years ago :) (I guess github notifications weren't really good). I can somehow see that this is useful. Can someone describe how to use this productively? Put caching everywhere and remove it on fast executing queries. I guess the problem is also using time and cache magics at the same time.

[dbeach24]

Hi Till. When deciding whether to cache something and the cost of recalculating, the time is often highly relevant and trivial to store. At the time I wrote this, I was doing research from several notebooks, and wanted to keep track of the time cost if I made changes to my data or parameters.

…

On Sat, Oct 8, 2022 at 9:13 AM Till Riedel ***@***.***> wrote: Somehow we missed this PR 4 years ago :) (I guess github notifications weren't really good). I can somehow see that this is useful. Can someone describe how to use this productively? Put caching everywhere and remove it on fast executing queries. I guess the problem is also using time and cache magics at the same time. — Reply to this email directly, view it on GitHub <#17 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACYRCIZ6IJSJEPLD6DQTSKLWCEUIZANCNFSM4GGEW2GQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>