Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optimize database requests #81

Open
dlareau opened this issue Jan 14, 2019 · 1 comment
Open

Optimize database requests #81

dlareau opened this issue Jan 14, 2019 · 1 comment
Labels
enhancement Hard Hard to implement Long term For systematic issues that won't be fixed in just one release.

Comments

@dlareau
Copy link
Owner

dlareau commented Jan 14, 2019

This is issue 2/3 spawned by closing #11.

There are places in the code where data is retrieved from the database with no care for what impact this has on the database load. This issue is to look over all of the codebase, identifying places where we are either over-requesting or under-requesting (and therefore causing more fetches later). One area this is currently really bad is the chat pages.

Also, the models in the database should get proper index labels for quicker lookup on more used fields.

@dlareau dlareau added enhancement Hard Hard to implement labels Jan 14, 2019
@dlareau dlareau added the Long term For systematic issues that won't be fixed in just one release. label Feb 8, 2019
@timparenti
Copy link
Contributor

Some related reading I found:
https://www.toptal.com/sql-server/sql-database-tuning-for-developers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Hard Hard to implement Long term For systematic issues that won't be fixed in just one release.
Projects
None yet
Development

No branches or pull requests

2 participants