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

Caching #2

Open
ErazerBrecht opened this issue Jan 18, 2016 · 2 comments
Open

Caching #2

ErazerBrecht opened this issue Jan 18, 2016 · 2 comments
Assignees

Comments

@ErazerBrecht
Copy link
Owner

We load the same data a lot of times.
Search the places where it isn't needed.

Than we could make take the previous result.

I already did it on the admin panel for the Users.
They shouldn't reload every time. Our dashboard is now smoother!

@ErazerBrecht ErazerBrecht self-assigned this Jan 19, 2016
@ErazerBrecht
Copy link
Owner Author

Changing our data service. This is done in another branch for now...
Evolved it into sort of a 'DAL'

Fixed @ the moment (Admin)

  • Users.
    • There aren't many times that there new registrations
    • Users don't need to be loaded every single time
    • Deleting a user => don't reload every user after changes happened in the DB, delete user in local array!
    • Assigning a user => don't reload every user after changes happened in the DB, change user in local array!
  • Exercises
    • There aren't many admins, reloading all the exercises constantly is not needed here!
    • Adding an exercise => no need for reloading every exercise after post, just add it in our local array! (Add Exercise #3)
  • Answers
    • These should be reload every time! Users can make any second a new answer
    • Add (cached) users when they are loaded! No need for reloading all the users. The site is not a lot faster!

@timdams & @tomptrs
Actually Meteor.js is a better solution for solving this performance issues! It has a build in local DB. Maybe for the students of next year?

@timdams
Copy link

timdams commented Jan 20, 2016

Genoteerd!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants