When we create a judging, either on initial submission or during a rejudging it is slow as we create all judging runs and corresponding judge tasks.
With the current amount of test cases, it takes around a second per judging which is confusingly slow.
Now, we could do some minimal amount of work (capturing the current run and compile config) and then create a judge task to create this data from the judge daemon.
One could even go one step further for rejudgings so that all of the judgings are created in a judgetask.
When we create a judging, either on initial submission or during a rejudging it is slow as we create all judging runs and corresponding judge tasks.
With the current amount of test cases, it takes around a second per judging which is confusingly slow.
Now, we could do some minimal amount of work (capturing the current run and compile config) and then create a judge task to create this data from the judge daemon.
One could even go one step further for rejudgings so that all of the judgings are created in a judgetask.