That’s not the case here, it’s been discussed a few times in various planning tasks, and in the code blog last year. There are just so many competing priorities that we haven’t gotten to implementing it yet. There are two possible caching implementations, automatic caching and a more user-oriented cache node. We’d like to have both, ideally. The recent developments on the geometry nodes evaluator will make this easier. One idea is to keep track of which of the node network’s inputs have changed and invalidate cached data when they change.