Back to Issue List

Smart, Customizable Log Caching

enhancement

Currently, several courses have gradebooks that are really slow because they need to loop over all of a student's activity to determine their scores. This is incredibly slow, and if enough students load their gradebook simultaneously, it can effectively accidentally act as a DoS attack. It would be nice to add a way to allow courses to specify information that should be cached for every problem (or for every user, or....).

Maybe this is a group of two functions:

I'll need to think a bit more about the form these functions take (and whether the above are the two types of caches that make sense). But it's a really nice idea that can prevent some progress/gradebook pages from being a really sticky river late in the semester.

Comments:

adam j hartz <hz@mit.edu> commented at 21 Jun 2019; 11:26 AM:

I think this depends on #25, since per-user-per-course logs can be huge, and the current log format is really slow on big objects.

Permalink

 

Back to Issue List