I use Datomic local for not so large database with some high churn attributes marked with noHistory.
I hadn’t been noticing degrading performance until I bumped some dependencies and deployed a new version of my app. For some attributes I found 1-2 thousand older versions are available which affects performance badly.
Are there some debug logs or something so I can figure what is going wrong?
1 Like
Hey @shashurup,
Can you share what version of Datomic local you are using? Also what storage protocol (is this a mem Datomic local db?)
Thanks!
Hi @jaret
I’ve recently updated to 1.0.277. By the time the attributes were accumulating it was mostly 1.0.267.
I use disk storage, i.e. :storage-dir …
1 Like
Same observation here. I’m using Datomic local 1.0.285 configured for file storage and even though all the attributes have noHistory true, the db file keeps growing (I have many high-churn attributes). I wonder whether it means noHistory has no effect in Datomic local or the db will be truncated after reaching some critical size?
1 Like