Shake spends predominant time reading its database

[srid]

With shakeTimings = True:

Function shake                    0.000s    0%
Database read                     0.894s   73%  =========================
With database                     0.072s    5%  ==
Running rules                     0.246s   20%  ======
Pool finished (1 threads, 1 max)  0.000s    0%
Cleanup                           0.000s    0%
Total                             1.212s  100%

Size of the database for this report:

$ du -sh .shake/
28M     .shake/
$

[srid]

Shake's cacheActionWith (added here) invokes cacheAction twice; once for the "key", and another for the "argument". In rib, the "key" is set to filename, and the "argument" is set to a tuple of filename and its contents. So effectively I think Shake is storing the file contents as a key in its cache. Since file contents are bound to change over time in a static site, we are seeing the Shake database grow in size over time as well.

So what is the solution here? 🤔