Is the time it takes to score getting longer?
\nI remember that when I submitted around April, I got my score back immediately. How about you?
Is the time it takes to score getting longer?
\nI remember that when I submitted around April, I got my score back immediately. How about you?
I'm getting results immediately. kkiller's notebook, for example, submits and scores in about 6 minutes.
\nIf anybody is looking for a teammate, please contact me from my profile.
", "rawMarkdown": "I'm getting results immediately. [kkiller's notebook](https://www.kaggle.com/kneroma/clean-fast-simple-bird-identifier-inference), for example, submits and scores in about 6 minutes.\n\n---\n*If anybody is looking for a teammate, please contact me from my [profile](https://www.kaggle.com/philipkd).*", "votes": null }, { "id": "1297362", "postDate": "05/08/2021 00:36:53", "content": "Are you sure? A recent submission by a team member took about an hour.
\nIt was long enough to make me worry.
\nI'm still submitting, so I'd like to include that time in my thinking.
\nThank you for your valuable input.
Yes, timed one last night, it took 6 minutes. I'm a bit obsessed with timing these notebooks, heh.
", "rawMarkdown": "Yes, timed one last night, it took 6 minutes. I'm a [bit obsessed with timing](https://www.kaggle.com/c/rsna-str-pulmonary-embolism-detection/discussion/192950) these notebooks, heh.", "votes": null }, { "id": "1297393", "postDate": "05/08/2021 01:23:46", "content": "Time still around the 5 minute mark for me BUT you need to remember a recent change where the submission start can be delayed because of kaggle workload - if your doing a submission a few minutes before the end of day that tends to be a very busy time for Kaggle and you might see a very slow response.
", "rawMarkdown": "Time still around the 5 minute mark for me BUT you need to remember a recent change where the submission start can be delayed because of kaggle workload - if your doing a submission a few minutes before the end of day that tends to be a very busy time for Kaggle and you might see a very slow response.", "votes": null }, { "id": "1297404", "postDate": "05/08/2021 02:03:02", "content": "I didn't know that the start would be delayed.
\nThank you very much.
\nWhere can I find that recent change?
Not sure were it's documented - I have gotten the message about it several times in the last weeks when doing a submit.
", "rawMarkdown": "Not sure were it's documented - I have gotten the message about it several times in the last weeks when doing a submit.", "votes": null }, { "id": "1298541", "postDate": "05/09/2021 02:04:36", "content": "I'm a team member of @udondon.
\nWhen I first submitted notebooks, I got my score in a few minutes,
\nbut now it takes about an hour to get my score.
I wondered why submission time is so long, and I compared our notebooks.
\nThen I found first notebook of mine was accelerated with GPU and recent one with CPU.
Dose it make difference of submission time?
", "rawMarkdown": "I'm a team member of @udondon.\n\nWhen I first submitted notebooks, I got my score in a few minutes,\nbut now it takes about an hour to get my score.\n\nI wondered why submission time is so long, and I compared our notebooks.\nThen I found first notebook of mine was accelerated with GPU and recent one with CPU.\n\nDose it make difference of submission time?", "votes": null }, { "id": "1298548", "postDate": "05/09/2021 02:22:24", "content": "It will have large difference if you are using deep neural nets.
", "rawMarkdown": "It will have large difference if you are using deep neural nets.", "votes": null }, { "id": "1298596", "postDate": "05/09/2021 03:52:02", "content": "I used deep neural nets, and that was the reason why it takes so long to submit notebooks!
\nThank you. I'll submit with GPU after this.
I just got this warning when committing:
\n\n\nCommits are changing
\n
\n Sometimes demand for resources in the Kaggle community exceeds our supply. If that happens when you save a notebook, we will run your commit later in the day as resources become available.It's a rare occurence but we wanted to let you know!
\n
With three competitions ending in the next few days I guess kaggle will be overloaded.
", "rawMarkdown": "I just got this warning when committing:\n\n> Commits are changing\n> Sometimes demand for resources in the Kaggle community exceeds our supply. If that happens when you save a notebook, we will run your commit later in the day as resources become available.\n> \n> It's a rare occurence but we wanted to let you know!\n\nWith three competitions ending in the next few days I guess kaggle will be overloaded.", "votes": null } ], "comments": [ { "id": 1297299, "author_name": "philipkd", "author_url": "", "post_date": "05/07/2021 22:24:50", "content": "I'm getting results immediately. kkiller's notebook, for example, submits and scores in about 6 minutes.
\nIf anybody is looking for a teammate, please contact me from my profile.
", "votes": null, "replies": [ { "id": 1297362, "author_name": "udondon", "author_url": "", "post_date": "05/08/2021 00:36:53", "content": "Are you sure? A recent submission by a team member took about an hour.
\nIt was long enough to make me worry.
\nI'm still submitting, so I'd like to include that time in my thinking.
\nThank you for your valuable input.
Yes, timed one last night, it took 6 minutes. I'm a bit obsessed with timing these notebooks, heh.
", "votes": null, "replies": [] } ] }, { "id": 1297393, "author_name": "pcjimmmy", "author_url": "", "post_date": "05/08/2021 01:23:46", "content": "Time still around the 5 minute mark for me BUT you need to remember a recent change where the submission start can be delayed because of kaggle workload - if your doing a submission a few minutes before the end of day that tends to be a very busy time for Kaggle and you might see a very slow response.
", "votes": null, "replies": [ { "id": 1297404, "author_name": "udondon", "author_url": "", "post_date": "05/08/2021 02:03:02", "content": "I didn't know that the start would be delayed.
\nThank you very much.
\nWhere can I find that recent change?
Not sure were it's documented - I have gotten the message about it several times in the last weeks when doing a submit.
", "votes": null, "replies": [] } ] }, { "id": 1298541, "author_name": "soule50431", "author_url": "", "post_date": "05/09/2021 02:04:36", "content": "I'm a team member of @udondon.
\nWhen I first submitted notebooks, I got my score in a few minutes,
\nbut now it takes about an hour to get my score.
I wondered why submission time is so long, and I compared our notebooks.
\nThen I found first notebook of mine was accelerated with GPU and recent one with CPU.
Dose it make difference of submission time?
", "votes": null, "replies": [ { "id": 1298548, "author_name": "jy2tong", "author_url": "", "post_date": "05/09/2021 02:22:24", "content": "It will have large difference if you are using deep neural nets.
", "votes": null, "replies": [] }, { "id": 1298596, "author_name": "soule50431", "author_url": "", "post_date": "05/09/2021 03:52:02", "content": "I used deep neural nets, and that was the reason why it takes so long to submit notebooks!
\nThank you. I'll submit with GPU after this.
I just got this warning when committing:
\n\n\nCommits are changing
\n
\n Sometimes demand for resources in the Kaggle community exceeds our supply. If that happens when you save a notebook, we will run your commit later in the day as resources become available.It's a rare occurence but we wanted to let you know!
\n
With three competitions ending in the next few days I guess kaggle will be overloaded.
", "votes": null, "replies": [] } ], "raw_markdown_by_id": { "1296924": "Is the time it takes to score getting longer?\nI remember that when I submitted around April, I got my score back immediately. How about you?", "1297299": "I'm getting results immediately. [kkiller's notebook](https://www.kaggle.com/kneroma/clean-fast-simple-bird-identifier-inference), for example, submits and scores in about 6 minutes.\n\n---\n*If anybody is looking for a teammate, please contact me from my [profile](https://www.kaggle.com/philipkd).*", "1297362": "Are you sure? A recent submission by a team member took about an hour. \nIt was long enough to make me worry.\nI'm still submitting, so I'd like to include that time in my thinking. \nThank you for your valuable input.", "1297368": "Yes, timed one last night, it took 6 minutes. I'm a [bit obsessed with timing](https://www.kaggle.com/c/rsna-str-pulmonary-embolism-detection/discussion/192950) these notebooks, heh.", "1297393": "Time still around the 5 minute mark for me BUT you need to remember a recent change where the submission start can be delayed because of kaggle workload - if your doing a submission a few minutes before the end of day that tends to be a very busy time for Kaggle and you might see a very slow response.", "1297404": "I didn't know that the start would be delayed. \nThank you very much. \nWhere can I find that recent change?", "1298188": "Not sure were it's documented - I have gotten the message about it several times in the last weeks when doing a submit.", "1298541": "I'm a team member of @udondon.\n\nWhen I first submitted notebooks, I got my score in a few minutes,\nbut now it takes about an hour to get my score.\n\nI wondered why submission time is so long, and I compared our notebooks.\nThen I found first notebook of mine was accelerated with GPU and recent one with CPU.\n\nDose it make difference of submission time?", "1298548": "It will have large difference if you are using deep neural nets.", "1298596": "I used deep neural nets, and that was the reason why it takes so long to submit notebooks!\nThank you. I'll submit with GPU after this.", "1299494": "I just got this warning when committing:\n\n> Commits are changing\n> Sometimes demand for resources in the Kaggle community exceeds our supply. If that happens when you save a notebook, we will run your commit later in the day as resources become available.\n> \n> It's a rare occurence but we wanted to let you know!\n\nWith three competitions ending in the next few days I guess kaggle will be overloaded." }, "source": "meta" }