Speed up assignments of achievements. #2711
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
drgrice1
force-pushed
the
assign-achievements-massive-speed-tweak
branch
5 times, most recently
from
b13a38f to
50e7de0
Compare
If you have payed attention (or tested openwebwork#2709 and openwebwork#2710), then you know that this takes a long time if there are a large number of users. Way to long to be at all reasonable. This uses techniques like those used for assigning multiple sets to users, i.e., the `WeBWorK::DB::Schema::NewSQL::Std::insert_records` and `WeBWorK::DB::Schema::NewSQL::Std::update_records` methods, to speed up assignment of achievements to users. This brings the assignment time for 5000 users down from more than 8 minutes, to less than 30 seconds.
drgrice1
force-pushed
the
assign-achievements-massive-speed-tweak
branch
from
50e7de0 to
524cb33
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If you have payed attention (or tested #2709 and #2710), then you know that this takes a long time if there are a large number of users. Way to long to be at all reasonable.
This uses techniques like those used for assigning multiple sets to users, i.e., the
WeBWorK::DB::Schema::NewSQL::Std::insert_recordsandWeBWorK::DB::Schema::NewSQL::Std::update_recordsmethods, to speed up assignment of achievements to users.This brings the assignment time for 5000 users down from more than 8 minutes, to less than 30 seconds.