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
When calling /ordinals/inscriptions, the "total" JSON key returns the number of results for the given filter set. When this number is very large, the SQL query will take a very long time to finish because Postgres has to count every single row before returning the total value.
To optimize this, we should keep a pre-calculated count of common filters such as mime_type for the most popular types. We currently only do this kind of caching for unfiltered queries (and it made a huge difference in performance).
The text was updated successfully, but these errors were encountered:
When calling
/ordinals/inscriptions
, the"total"
JSON key returns the number of results for the given filter set. When this number is very large, the SQL query will take a very long time to finish because Postgres has to count every single row before returning the total value.To optimize this, we should keep a pre-calculated count of common filters such as
mime_type
for the most popular types. We currently only do this kind of caching for unfiltered queries (and it made a huge difference in performance).The text was updated successfully, but these errors were encountered: