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
I'm taking this picture as an example. We can see that we just test whether this table exists and check whether it's a system table. But the TableInfoByID will try to get the whole table meta of the given table id and it's possible to read things from storage and then do the json decoding. There'll be huge costs once it needs to query from the storage.
We can avoid the possible network cost to get the whole table meta from storage.
The text was updated successfully, but these errors were encountered:
All three major background jobs(Update Memory Objs, Dump Count/ModifyCount to Storage, GC stats of deleted tables) can save most of the network cost by avoiding reading the full table meta of tables.
By testing against #57844 (2025.01.22 version), both the Update job and the Dump Delta to Storage worker can reduce their running time from minutes to seconds.
As a side benefit, the total time of the rolling update will be saved too.
Enhancement
I'm taking this picture as an example. We can see that we just test whether this table exists and check whether it's a system table. But the
TableInfoByID
will try to get the whole table meta of the given table id and it's possible to read things from storage and then do the json decoding. There'll be huge costs once it needs to query from the storage.We can avoid the possible network cost to get the whole table meta from storage.
The text was updated successfully, but these errors were encountered: