![\"\"](\"https://www.googleapis.com/download/storage/v1/b/kaggle-forum-message-attachments/o/inbox%2F1192725%2Fbee745ea25cd637dec0b083292983564%2F1ef84cacfe6a3fad8cbd2578bed3e6cd.png?generation=1610023245487345&alt=media\")
Typically, my kernel runs for about 2-3 hours. After I added some basic processing procedures (without changing the model), there was no exception in the test, but there was a timeout problem on submit (an error was reported after 9 hours), does anyone have the same problem?
\n如果输入文件39.98g ，加上输出文件大于了40g（磁盘)，提交后会导致错误吗？
找到原因了。似乎官方把循环的第二个sample_prediction_df 变量在昨天改掉了。之前我用这个变量提交的。
", "messages": [ { "id": "1141444", "postDate": "01/06/2021 17:59:19", "content": "Typically, my kernel runs for about 2-3 hours. After I added some basic processing procedures (without changing the model), there was no exception in the test, but there was a timeout problem on submit (an error was reported after 9 hours), does anyone have the same problem?
\n如果输入文件39.98g ，加上输出文件大于了40g（磁盘)，提交后会导致错误吗？
找到原因了。似乎官方把循环的第二个sample_prediction_df 变量在昨天改掉了。之前我用这个变量提交的。
", "rawMarkdown": "Typically, my kernel runs for about 2-3 hours. After I added some basic processing procedures (without changing the model), there was no exception in the test, but there was a timeout problem on submit (an error was reported after 9 hours), does anyone have the same problem?\n如果输入文件39.98g ，加上输出文件大于了40g（磁盘)，提交后会导致错误吗？\n\n找到原因了。似乎官方把循环的第二个sample_prediction_df 变量在昨天改掉了。之前我用这个变量提交的。", "votes": null }, { "id": "1141520", "postDate": "01/06/2021 18:37:44", "content": "your iteration could be taking more than 550 ms every iteration
", "rawMarkdown": "your iteration could be taking more than 550 ms every iteration", "votes": null }, { "id": "1141526", "postDate": "01/06/2021 18:41:16", "content": "\bMy model took about 2-3 hours to run before the problem occurred, and the processing I added was simple. Almost no extra time is required。
", "rawMarkdown": "\bMy model took about 2-3 hours to run before the problem occurred, and the processing I added was simple. Almost no extra time is required。", "votes": null }, { "id": "1141549", "postDate": "01/06/2021 18:57:09", "content": "do %%timeit on that block of code and check how many ms you add to
", "rawMarkdown": "do %%timeit on that block of code and check how many ms you add to", "votes": null }, { "id": "1141559", "postDate": "01/06/2021 19:02:02", "content": "Using the simulator to test （250W data）, run in 2 hours and 40 minutes
", "rawMarkdown": "Using the simulator to test （250W data）, run in 2 hours and 40 minutes", "votes": null }, { "id": "1141846", "postDate": "01/06/2021 23:43:57", "content": "For me, it is the same. If you find any solution, please share it…
", "rawMarkdown": "For me, it is the same. If you find any solution, please share it...", "votes": null }, { "id": "1141871", "postDate": "01/07/2021 00:38:52", "content": "I wasted four commits yesterday to test this issue, including one that was successful (it used to be 2hour 4G memory), now I can almost tell it's a platform issue, I'm going to test a full 0 or 1 commits again at noon.
\n@sohier
I have read someone says if your kernel gets out of memory error, your kernel shows an error after 9 hours, not at the time OOM error occurred.
", "rawMarkdown": "I have read someone says if your kernel gets out of memory error, your kernel shows an error after 9 hours, not at the time OOM error occurred.", "votes": null }, { "id": "1141948", "postDate": "01/07/2021 03:05:45", "content": "thanks ，i will check again again again
", "rawMarkdown": "thanks ，i will check again again again", "votes": null }, { "id": "1142514", "postDate": "01/07/2021 12:44:09", "content": "
help!!!please ,
\nI have given up checking and debugging. I have tried very hard to find the problem in my kernel.
\nOr I might choose to use the rest of the time to try some regular commits to prove that the problem itself exists.
your iteration could be taking more than 550 ms every iteration
", "votes": null, "replies": [ { "id": 1141526, "author_name": "infturing", "author_url": "", "post_date": "01/06/2021 18:41:16", "content": "\bMy model took about 2-3 hours to run before the problem occurred, and the processing I added was simple. Almost no extra time is required。
", "votes": null, "replies": [] }, { "id": 1141549, "author_name": "jaideepvalani", "author_url": "", "post_date": "01/06/2021 18:57:09", "content": "do %%timeit on that block of code and check how many ms you add to
", "votes": null, "replies": [] }, { "id": 1141559, "author_name": "infturing", "author_url": "", "post_date": "01/06/2021 19:02:02", "content": "Using the simulator to test （250W data）, run in 2 hours and 40 minutes
", "votes": null, "replies": [] } ] }, { "id": 1141846, "author_name": "lhagiimn", "author_url": "", "post_date": "01/06/2021 23:43:57", "content": "For me, it is the same. If you find any solution, please share it…
", "votes": null, "replies": [ { "id": 1141871, "author_name": "infturing", "author_url": "", "post_date": "01/07/2021 00:38:52", "content": "I wasted four commits yesterday to test this issue, including one that was successful (it used to be 2hour 4G memory), now I can almost tell it's a platform issue, I'm going to test a full 0 or 1 commits again at noon.
\n@sohier
I have read someone says if your kernel gets out of memory error, your kernel shows an error after 9 hours, not at the time OOM error occurred.
", "votes": null, "replies": [ { "id": 1141948, "author_name": "infturing", "author_url": "", "post_date": "01/07/2021 03:05:45", "content": "thanks ，i will check again again again
", "votes": null, "replies": [] } ] }, { "id": 1142514, "author_name": "infturing", "author_url": "", "post_date": "01/07/2021 12:44:09", "content": "
help!!!please ,
\nI have given up checking and debugging. I have tried very hard to find the problem in my kernel.
\nOr I might choose to use the rest of the time to try some regular commits to prove that the problem itself exists.