can you please do something about the time it is taking to run the code!
@yashpawar_21 Can you be more specific about what step is taking a long time and what error you are seeing? Is your code loaded but waiting in the queue? Or is it slow after your code has begun to execute?
My first recommendation is make sure to test your submission locally and with a smoke test before submitting on the full test set. Then you can uncover errors more quickly. It also helps with conscientious use of the shared compute resources, and makes sure your code will run without error before running on the full test set.
I guess he means the pending time takes too long. When I submitted it around 11 hours ago, there were 7 submissions ahead, but there are still 4 submissions ahead.
Exactly I mistakenly submitted the wrong file and just because of slight error i had to wait 12 hours for that submission kindly do something about this , so that system runs submissions parallelly
@yashpawar_21 @dylanliu We’ve added a second node to the code execution cluster, so you should see submissions moving more quickly now. Thanks for flagging the long queue.
We’ll keep an eye on wait times, but feel free to let us know if this continues to be an isuse
1 Like
We also added a separate cluster for smoke tests, so smoke tests will not have to wait on long-running full submissions and should have consistently short wait times.
2 Likes