jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-19 07:17:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

2022.6: Finialize database performance

Browse Source
This commit is contained in:
Franck Nijhof 2022-06-01 11:07:21 +02:00
parent 2b282bc98f
commit d6a72be5d2
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3
1 changed files with 12 additions and 23 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

35
source/_posts/2022-06-01-release-20226.markdown
View File

@ -217,34 +217,23 @@ still add the entire device if you want to.
## Database performance ## Database performance
{% details "TODO" %} This release builds on [the database improvements from 2022.4](/blog/2022/04/06/release-20224/#database-performance).
Disk writes have been reduced to preserve SD card lifetimes and new APIs,
- Not sure yet about the TODO even which get event/historical data to the frontend even faster.
{% enddetails %}
This release builds on the improvements from 2022.4, which offers disk write
reductions intended to preserve SD card lifetimes and features a new WebSocket
API for both history and logbook, which gets data to the frontend even faster.
The database storage format is further optimized, with an additional size The database storage format is further optimized, with an additional size
reduction ranging from 25-40% for most installs on top of what 2022.4 brought. reduction ranging from 25-40% for most installs on top of what has been gained
in previous releases. This is achieved by storing events more efficiently.
When the same event data already exists in the database, newly recorded events Data stored in the database before upgrading to this release isn't compacted.
now only store a reference to the event data instead of saving the whole event The size reduction will occur over time when new data gets recorded, and older
data. data gets purged.
As data stored in the database before 2022.6 does not get updated, the If you are using SQLite (default) or MySQL, you will benefit from a faster date
reduction in database size will occur over time with the recording of new data parser, which speeds up multi-hour history and logbooks.
and the purging of old data. If you have `auto_repack` enabled in the recorder,
you'll start to see the size reductions on the second Sunday of the month after
you update.
SQLite and MySQL users benefit from a faster date parser, which speeds up We recommend not to miss this release to ensure that future database changes
multi-hour history and logbook queries. and migrations will be faster.
Don't miss this release, as future database migrations will be faster if most
of your data is in the new format.
## Other noteworthy changes ## Other noteworthy changes