You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AlexVasiluta opened this issue
Feb 3, 2025
· 0 comments
Labels
contentIssue regarding content on the main instance, not necessarily related to code/infrastructuretechnicalPurely technical backend issue, virtually nothing frontend-facing
This is essential to continue scaling up the platform and to minimize issues with inconsistency in evaluation. A many-to-many architecture should be the end goal, where multiple instances can talk with multiple remote runners. The biggest problem remains how to efficiently send huge test input files and receive huge test output files over the wire and how to handle reassigning of workers.
The text was updated successfully, but these errors were encountered:
AlexVasiluta
added
content
Issue regarding content on the main instance, not necessarily related to code/infrastructure
technical
Purely technical backend issue, virtually nothing frontend-facing
labels
Feb 3, 2025
contentIssue regarding content on the main instance, not necessarily related to code/infrastructuretechnicalPurely technical backend issue, virtually nothing frontend-facing
This is essential to continue scaling up the platform and to minimize issues with inconsistency in evaluation. A many-to-many architecture should be the end goal, where multiple instances can talk with multiple remote runners. The biggest problem remains how to efficiently send huge test input files and receive huge test output files over the wire and how to handle reassigning of workers.
The text was updated successfully, but these errors were encountered: