# Datomic 1.0.6527 now available

**URL:** <https://forum.datomic.com/t/datomic-1-0-6527-now-available/2143>\
**Category:** Announcements\
**Created:** [October 19, 2022, 11:56am UTC](https://forum.datomic.com/t/datomic-1-0-6527-now-available/2143 "2022-10-19T11:56:14Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jaret](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.datomic.com/jaret/32/45_2.png) [@jaret](https://forum.datomic.com/u/jaret)\
**Post date:** [October 19, 2022, 11:56am UTC](https://forum.datomic.com/t/datomic-1-0-6527-now-available/2143/1 "2022-10-19T11:56:14Z")

</div>

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

## 1.0.6527: 2022/10/21

- Feature: io-stats for transactions and queries. See [https://docs.datomic.com/on-prem/api/io-stats.html](https://docs.datomic.com/on-prem/api/io-stats.html).
- Feature: Verify backups without performing a restore. See [https://docs.datomic.com/on-prem/operation/backup.html#verifying-backups](https://docs.datomic.com/on-prem/operation/backup.html#verifying-backups).
- Performance: Improved peer adoption of new indexes.
- Performance: improved performance (throughput and $) for differential backups to S3.
- Performance: Datomic now uses caffeine instead of guava for the object cache.
- Performance improvements for valcache and the object cache.
- Performance: limit thread and memory usage when transactor is adding an AVET index ([https://docs.datomic.com/on-prem/schema/schema-change.html#adding-avet-index](https://docs.datomic.com/on-prem/schema/schema-change.html#adding-avet-index)).
- Fix: Peer no longer resolves lookup refs before sending tx data to transactor.
- Fix: Attribute names that begin with an underscore can be used for forward lookups in entity and pull. Note that naming attributes with a leading underscore is strongly discouraged because it conflicts with the convention for reverse lookup.