{ "id": 376058, "title": "How can we know if the notebook run-time <= 9 hours？", "url": "/competitions/rsna-breast-cancer-detection/discussion/376058", "author_name": "BarryZhou", "post_date": "2023-01-04T15:29:25.514000", "votes": 2, "comment_count": 5, "views": 0, "content": "

Code Requirements:
\nCPU Notebook <= 9 hours run-time
\nGPU Notebook <= 9 hours run-time
\nSo how can we know if the notebook run-time <= 9 hours？

", "messages": [ { "id": 2086577, "postDate": "2023-01-04T20:49:06.080Z", "content": "

I have seen two ways to track time -
\nhttps://www.kaggle.com/code/yasufuminakama/fb3-submission-time

\n

https://www.kaggle.com/competitions/riiid-test-answer-prediction/discussion/201047

", "rawMarkdown": "I have seen two ways to track time - \nhttps://www.kaggle.com/code/yasufuminakama/fb3-submission-time \n\nhttps://www.kaggle.com/competitions/riiid-test-answer-prediction/discussion/201047\n", "votes": 1, "replies": [ { "id": 2086582, "postDate": "2023-01-04T20:54:49.797Z", "content": "

Thanks. Y I had done my own variant of the 2nd approach… Still would be nice if kaggle would add the functionality…

", "rawMarkdown": "Thanks. Y I had done my own variant of the 2nd approach... Still would be nice if kaggle would add the functionality... ", "votes": 1, "replies": [ { "id": 2086597, "postDate": "2023-01-04T21:03:57.617Z", "content": "

I agree, a similar discussion earlier had this answer by Kaggle Staff

\n
\n

I can confirm the reason that we don't show times is to limit their utility in automated/high-volume probing. There are a couple channels where information can leak out--error messages, errored vs. not, submission timing--so we try to strike a balance between providing some debugging information without allowing too much information exfiltration.

\n
", "rawMarkdown": "I agree, a similar discussion earlier had [this answer by Kaggle Staff ](https://www.kaggle.com/competitions/AI4Code/discussion/342035#1886231 )\n\n>I can confirm the reason that we don't show times is to limit their utility in automated/high-volume probing. There are a couple channels where information can leak out--error messages, errored vs. not, submission timing--so we try to strike a balance between providing some debugging information without allowing too much information exfiltration.\n\n", "votes": 2 } ] } ] }, { "id": 2086168, "postDate": "2023-01-04T16:01:46.597Z", "content": "

Otherwise it says Timeout.

", "rawMarkdown": "Otherwise it says Timeout.", "votes": 2 }, { "id": 2086129, "postDate": "2023-01-04T15:29:25.513Z", "content": "

Code Requirements:
\nCPU Notebook <= 9 hours run-time
\nGPU Notebook <= 9 hours run-time
\nSo how can we know if the notebook run-time <= 9 hours？

", "rawMarkdown": "Code Requirements: \n**CPU Notebook <= 9 hours run-time**\n**GPU Notebook <= 9 hours run-time**\nSo how can we know if the notebook run-time <= 9 hours？", "votes": 2 }, { "id": 2086174, "postDate": "2023-01-04T16:06:49.903Z", "content": "

It would be great if Kaggle would track how long it takes to run a submission and provide that along with the score.

", "rawMarkdown": "It would be great if Kaggle would track how long it takes to run a submission and provide that along with the score." } ], "comments": [ { "id": 2086577, "author_name": "RB", "author_url": "", "post_date": "2023-01-04T20:49:06.080000", "content": "

I have seen two ways to track time -
\nhttps://www.kaggle.com/code/yasufuminakama/fb3-submission-time

\n

https://www.kaggle.com/competitions/riiid-test-answer-prediction/discussion/201047

", "votes": 1, "replies": [ { "id": 2086582, "author_name": "John Robinson", "author_url": "", "post_date": "2023-01-04T20:54:49.797000", "content": "

Thanks. Y I had done my own variant of the 2nd approach… Still would be nice if kaggle would add the functionality…

", "votes": 1, "replies": [ { "id": 2086597, "author_name": "RB", "author_url": "", "post_date": "2023-01-04T21:03:57.617000", "content": "

I agree, a similar discussion earlier had this answer by Kaggle Staff

\n
\n

I can confirm the reason that we don't show times is to limit their utility in automated/high-volume probing. There are a couple channels where information can leak out--error messages, errored vs. not, submission timing--so we try to strike a balance between providing some debugging information without allowing too much information exfiltration.

\n
", "votes": 2, "replies": [] } ] } ] }, { "id": 2086168, "author_name": "Kirderf", "author_url": "", "post_date": "2023-01-04T16:01:46.597000", "content": "

Otherwise it says Timeout.

", "votes": 2, "replies": [] }, { "id": 2086174, "author_name": "John Robinson", "author_url": "", "post_date": "2023-01-04T16:06:49.903000", "content": "

It would be great if Kaggle would track how long it takes to run a submission and provide that along with the score.

", "votes": 0, "replies": [] } ], "raw_markdown_by_id": { "2086577": "I have seen two ways to track time - \nhttps://www.kaggle.com/code/yasufuminakama/fb3-submission-time \n\nhttps://www.kaggle.com/competitions/riiid-test-answer-prediction/discussion/201047\n", "2086168": "Otherwise it says Timeout.", "2086129": "Code Requirements: \n**CPU Notebook <= 9 hours run-time**\n**GPU Notebook <= 9 hours run-time**\nSo how can we know if the notebook run-time <= 9 hours？", "2086174": "It would be great if Kaggle would track how long it takes to run a submission and provide that along with the score." } }