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
Currently we can not be sure whether some index (say, MY_INDEX_A) is ever in use or not.
All indexes decrease performance (more or less) of inserts and updates and also they all will be handled by GC that can take significant time.
So the rule of thumb is simple: do not create index "just in case". But in real prod systems this rule often is violated and one can hard to find where some index 'X' is used.
It will be useful if trace config will contain something like 'INDEX_FILTER <my_index_name1 | my_index_name2 | %my_pattern%>' for such logging.
The text was updated successfully, but these errors were encountered:
When there is a doubt about whether some index is ever selected by FB optimizer or not - it will be good idea to add it's name to trace config list of arguments for special (new) parameter.
PS. Sorry, my english is bad. If this word - 'preliminary' - isn`t properly used please remove it from the header of ticked.
Submitted by: @pavel-zotov
Currently we can not be sure whether some index (say, MY_INDEX_A) is ever in use or not.
All indexes decrease performance (more or less) of inserts and updates and also they all will be handled by GC that can take significant time.
So the rule of thumb is simple: do not create index "just in case". But in real prod systems this rule often is violated and one can hard to find where some index 'X' is used.
It will be useful if trace config will contain something like 'INDEX_FILTER <my_index_name1 | my_index_name2 | %my_pattern%>' for such logging.
The text was updated successfully, but these errors were encountered: