Closed Bug 1054277 Opened 10 years ago Closed 5 years ago

Review use of slow counts on MySQL

Categories

(developer.mozilla.org Graveyard :: Performance, defect)

Product:
developer.mozilla.org Graveyard
Component:
Performance
Platform:
All
Other
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: jezdez, Unassigned)

References

Details

(Whiteboard: [specification][type:change])

What feature should be changed? Please provide the URL of the feature if possible. ================================================================================== We could probably use https://github.com/educreations/django-mysql-fuzzycount/ for reducing the amount of time we spend asking the database for counts. Should make exists() calls faster, too. What problems would this solve? =============================== Slow counts Who would use this? =================== n/a What would users see? ===================== Faster pages! What would users do? What would happen as a result? =================================================== Dancing. Is there anything else we should know? ======================================
See Also: → 1159930
We've started to use django-mysql as part of the attachments refactor, so we could use its approx_count() method now: http://django-mysql.readthedocs.org/en/latest/queryset_extensions.html#django_mysql.models.approx_count
Component: General → Performance
MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.