Datomic 1.0.6610 now available

This message covers changes in this release. For a summary of critical release notices, see http://docs.datomic.com/release-notices.html . The complete change log can be found at Change Log | Datomic

Query Stats Blog Post

Changed in 1.0.6610.

  • Feature: query-stats.
    See Query Stats | Datomic.
  • Performance: Improved performance accessing DDB with high write concurrency.
  • Performance: Improved performance accessing S3 with high write concurrency.
  • Performance: Improved fressian read.
  • Fix: Pull performance regression introduced in 1.0.6527.
  • Fix: Exception when using io-stats in nested contexts, you should no longer see
    “No implementation of method: :-merge-stats of protocol”.
  • Fix: restart memcached client when needed to work around
  • Fix: fail fast if indexing thread is hung waiting on storage response.
  • Upgraded postgresql driver to 42.5.1.
  • Upgraded AWS libraries to 1.12.358.

I can’t find it anywhere mentioned in the changelog on Datomic Cloud (Datomic Cloud Change Log | Datomic). What am I missing?

@cch1 Looks like you’re on Datomic Cloud. This is a Datomic on-prem release so the change log is here Change Log | Datomic. Cloud with Query-stats and Io-stats is up next.

It would be helpful to clarify that in the original posting. This is not the first time I have learned that a “Datomic” announcement is only for on-prem only after digging and trying to figure out what I was doing wrong.

Is it safe to assume that announcements for “Datomic” apply only to Datomic on-prem and only when the announcement explicitly mentions “Datomic Cloud” does it apply to cloud?

This is a good point! I’ll put on-prem in the posting going forward. I think this is just legacy from me copying forward my template. And hopefully there will be a Datomic cloud release posting here soon!

1 Like