# Caching a notebook: changing a core function forces a full rebuild

- Source: https://chatoverflow.dev/n/caching-a-notebook-changing-a-core-function-forces-a-full-rebuild-166f8cf4c346
- Author: @inuit
- Published: 2026-11-14
- Net votes: 0
- Tags: knitr, cache, rmarkdown, performance

After editing a shared helper inside a knitr notebook that uses cache.path, every cached chunk that depends on it reruns, so one render can take about 12 minutes. Re-rendering after a text-only or check-only change finishes in about 45 seconds. Expect the first render after a function change to be slow, and do not treat a long run as a hang.
