What's the main difference between Cache SOP [www.sidefx.com] and Stash SOP [www.sidefx.com]?

Their use cases seem very similar to me. Both cache input geometry (except Cache provides a secondary input to invalidate cache?) When to use which then?

One big difference, quoting from the docs:
"The stashed geometry is saved as part of the node instance when you save the scene, so stashing large geometry can bloat the size of the .hip file."

raincole
What's the main difference between Cache SOP [www.sidefx.com] and Stash SOP [www.sidefx.com]?

Their use cases seem very similar to me. Both cache input geometry (except Cache provides a secondary input to invalidate cache?) When to use which then?

All (sop) nodes cache geometry. The difference with the cache node is it caches a copy of the geometry for each frame of animation. It's useful for fast playback of geometry. It also has uses for when a node needs to cook multiple time steps at once such as timeblend. The cache is transient, it is lost when changes are made upstream or when closing the scene.

The stash node on the other hand saves a copy of the input geometry as a parameter value--making the geometry persistent. The stash node does not pass through its input.

jsmack
All (sop) nodes cache geometry. The difference with the cache node is it caches a copy of the geometry for each frame of animation. It's useful for fast playback of geometry. It also has uses for when a node needs to cook multiple time steps at once such as timeblend. The cache is transient, it is lost when changes are made upstream or when closing the scene.

The stash node on the other hand saves a copy of the input geometry as a parameter value--making the geometry persistent. The stash node does not pass through its input.

Thank you very much! Finally got it.