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
We're running a Django application using joeflow and noticed that the joeflow_task_modified_a7cae80a index is big (103 MB in our case), making it the heaviest database indexes we have on one of the services.
The number of tasks is not that significant.
DATABASE=> SELECT COUNT(*) FROM joeflow_task;
count
---------
2496686
(1 row)
So one question I had, Is the index on the modified field actually needed for joeflow's internal operations?
I am not sure about your opinion on the indexes in this package (overall, joeflow has quite a lot of them leading the table of records, haha), is this something we can iterate on?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hey @codingjoe !
Thanks again for the package. :)
We're running a Django application using joeflow and noticed that the
joeflow_task_modified_a7cae80a
index is big (103 MB in our case), making it the heaviest database indexes we have on one of the services.The number of tasks is not that significant.
So one question I had, Is the index on the
modified
field actually needed for joeflow's internal operations?I am not sure about your opinion on the indexes in this package (overall, joeflow has quite a lot of them leading the table of records, haha), is this something we can iterate on?
Cheers,
Rust
Beta Was this translation helpful? Give feedback.
All reactions