Improve speed by caching the last few dataview queries

[MaxMoldmann]

Is your feature request related to a problem? Please describe.
My fault with 1500+ notes is loading Dataview queries slower and slower.

Describe the solution you'd like
One potential solution would be #1221 or to cache the results of the last few query runs and then serve them from cache if they are only a few minutes old. Add an option to manually run a query again - in case I added a new note and want it to show up despite the cache.

Describe alternatives you've considered
A more difficult solution would be a cache with an invalidation strategy, where Dataview keeps track of the last few changes in Links or Tags and then only serves a query from the Cache if the entry is not affected by recent changes.

[holroy]

Would it be possible to see some of the queries which are running slowly in your setup? Do you think they could be rewritten/reorder, so that you eliminate more of the file set earlier on in the query?

From personal experience careful ordering of the clauses can do magic when it comes to execution speed.

[MaxMoldmann]

Every Map of Content / Category page dynamically lists: Sub-Categories, Sub-Notes and other Notes that Link to this Note:

Sub-Categories

LIST WITHOUT ID link(file.name, title)
FROM #Category
WHERE contains(up, [[]])
SORT file.name ASC

Sub-Notes

LIST WITHOUT ID link(file.name, title) 
FROM !#Category
WHERE contains(up, [[]])
SORT file.name ASC

Linked Notes

LIST WITHOUT ID link(file.name, title) 
FROM [[]] AND !outgoing([[]]) AND !#Category
WHERE !contains(up, [[]])
SORT file.name ASC

[MaxMoldmann]

On central topics with many notes it takes roughly 3 seconds to display the dynamic DataView content on an Intel i7 @ 2.5 GHz. Smaller topics render almost instantly. I have to note though that on an M3 MacBook loading time is negligible everywhere.