Storable actions are helpful if you have two or more components that you navigate back-and-forth and they call the same Apex method. Marking them as storable allows you to retrieve the values from the cache, instead of making server trips every time.

If you are performing filtering and pagination of data, then marking an action as storable makes a lot of sense, because you know that user interactions can be in bursts of short spans, and performance can be improved by caching the data, instead of retrieving it from the server each time.

Also remember that actions involving DML (create, edit, or delete) do not mark the action as storable, since you want a fresh set of data entered by the user to save the database, and not the cached results.