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
Problem description and steps to reproduce
In your recent PR, a change was made to the query within DatabaseIntrospection.get_table_list, introducing complexity such as JOINs to support database comments. This modification has resulted in a significant increase in CPU usage, particularly noticeable on large database schemas. Upon investigation, it was found that the complex query is causing our database to consistently utilize over 90% CPU, leading to performance degradation.
Given that DatabaseIntrospection.get_table_list is utilized extensively within Django's source code, avoiding its usage isn't feasible. Therefore, I propose adding an option to exclude database comments retrieval, potentially by checking DatabaseFeatures.supports_comments within the get_table_list method. This would provide a solution for mitigating the performance impact caused by the complex query.
Thank you for considering this enhancement.
The text was updated successfully, but these errors were encountered:
Software versions
Problem description and steps to reproduce
In your recent PR, a change was made to the query within
DatabaseIntrospection.get_table_list
, introducing complexity such as JOINs to support database comments. This modification has resulted in a significant increase in CPU usage, particularly noticeable on large database schemas. Upon investigation, it was found that the complex query is causing our database to consistently utilize over 90% CPU, leading to performance degradation.Given that
DatabaseIntrospection.get_table_list
is utilized extensively within Django's source code, avoiding its usage isn't feasible. Therefore, I propose adding an option to exclude database comments retrieval, potentially by checkingDatabaseFeatures.supports_comments
within theget_table_list
method. This would provide a solution for mitigating the performance impact caused by the complex query.Thank you for considering this enhancement.
The text was updated successfully, but these errors were encountered: