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
Requests to the summary url were timing out, and i found that the culprit was some long-running queries. In my particular case, there are over 9000 Request records and approximately 79,000 SQLQuery records. i did a simple inspection on how long each part of the template context took to compute in this particular case, and pasted the results here:
Requests to the
summary
url were timing out, and i found that the culprit was some long-running queries. In my particular case, there are over 9000Request
records and approximately 79,000SQLQuery
records. i did a simple inspection on how long each part of the template context took to compute in this particular case, and pasted the results here:num_requests
: (9357) 0.004221200942993164 secondsnum_profiles
: (1903) 0.0025479793548583984 secondsavg_num_queries
: (8.44) 65.66700839996338 secondsavg_time_spent_on_queries
: (417) 65.6366651058197 secondsavg_overall_time
: (985) 0.011739730834960938 secondslongest_queries_by_view
: 0.030451536178588867 secondsmost_time_spent_in_db
: 262.45237922668457 secondsmost_queries
: 327.8772532939911 secondsAs you can see, some of the computations were very expensive. Perhaps there are more efficient ways of getting the same results.
Methodology:
The text was updated successfully, but these errors were encountered: