You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From research into KDP deserialization performance:
I think this graph of the KDP prod database IO is interesting. Currently, a sync is deserializing. The units in the graph are seconds of IO Wait per second. So I interpret that anything over 1 s/s essentially means the IO Wait is compounding. It's almost entirely reads, and so it seems this is likely caused by sequential reads of the morango store (without index). The query that I see filters on several columns, and so a full compound index would be gigantic, but a targeted index on the same columns with the constraint on dirty_bit = True should theoretically be plenty small with frequent deserializations. And it should speed it up a lot if the planner decides it's able to use the index
Since we dropped support for anything older than Django 3, we can now add a conditional index through Django
Description and outcomes
Add a conditional index on profile, model_name, partition, and dirty_bit with the condition that dirty_bit = True
Ensure this works with SQLite with the test suite we added to test older versions of SQLite
Overview
From research into KDP deserialization performance:
Since we dropped support for anything older than Django 3, we can now add a conditional index through Django
Description and outcomes
profile
,model_name
,partition
, anddirty_bit
with the condition thatdirty_bit = True
The text was updated successfully, but these errors were encountered: