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.

Sign up for GitHub

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

Jump to bottom

Batch scheduling bridge call #1501

Closed
Xyene opened this issue Aug 9, 2020 · 1 comment
Closed

Batch scheduling bridge call #1501

Xyene opened this issue Aug 9, 2020 · 1 comment
Labels
bridge optimization performance

Comments

@Xyene
Copy link
Member

Xyene commented Aug 9, 2020

Currently, if the site wishes to schedule N submissions for rejudging, it must make N bridge API calls. This can be very slow when N is large (enough so that there is a Celery screen for it), and can be alleviated by exposing batch scheduling functionality.
@Xyene
Copy link
Member Author

Xyene commented Aug 9, 2020

Closing as duplicate of #1318, which I somehow missed while filing this.

@Xyene Xyene closed this as completed Aug 9, 2020
Ninjaclasher added a commit to Ninjaclasher/site that referenced this issue Mar 21, 2022
@Ninjaclasher
Implement batch scheduling bridge call; fixes DMOJ#1501
61b7433
Ninjaclasher added a commit to Ninjaclasher/site that referenced this issue Mar 21, 2022
@Ninjaclasher
Implement batch scheduling bridge call; fixes DMOJ#1501
a4387f6
Ninjaclasher added a commit to Ninjaclasher/site that referenced this issue Mar 21, 2022
@Ninjaclasher
Implement batch scheduling bridge call; fixes DMOJ#1501
365c93a
Ninjaclasher added a commit to Ninjaclasher/site that referenced this issue Mar 21, 2022
@Ninjaclasher
Implement batch scheduling bridge call; fixes DMOJ#1501
03a71fd
@Ninjaclasher Ninjaclasher mentioned this issue Mar 21, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bridge optimization performance
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Xyene