Details
-
Type:
Improvement
-
Status:
New
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: Current Version
-
Fix Version/s: None
-
Component/s: OIOIOI
-
Labels:None
Description
Currently teachers are able to make mass rejudges (via selecting submissions in submissions tab). In case of small rejudges (<100submissions) this is not a problem. When bigger rejudges occur, filetracker2 dies due to big number of requests from Workers.
In perfect scenario we would replace the inefficient storage backend, but it would require a bit of work. Current workaround is to decrease CONCURENCY in settings.py, but it might be a nice feature to be able to control access to this (mass rejudge) feature.
One way I was thinking to implement it is adding a predicate can_mass_rejudge w ContestController getting a request and rejudge order. One can override its behavior per ContestController basis.
In perfect scenario we would replace the inefficient storage backend, but it would require a bit of work. Current workaround is to decrease CONCURENCY in settings.py, but it might be a nice feature to be able to control access to this (mass rejudge) feature.
One way I was thinking to implement it is adding a predicate can_mass_rejudge w ContestController getting a request and rejudge order. One can override its behavior per ContestController basis.
