{
  "id": 132273,
  "title": "Submission error: Exceeded allowed compute",
  "url": "/competitions/deepfake-detection-challenge/discussion/132273",
  "author_name": "",
  "post_date": "2020-02-25T06:35:53.058851300Z",
  "votes": 1,
  "comment_count": 6,
  "views": 0,
  "content": "<p><img src=\"https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F2716545%2F2a97fda2c91f68b3caadc42353f77fa4%2FWX20200225-143118.png?generation=1582612384525084&amp;alt=media\" alt=\"\">\nAfter clicking the submission button, it ran for about an hour smoothly, and here is the error called \"<strong>Exceeded allowed compute</strong>\", do you guys have any idea how to solve this kind of problem? Thanks in advance.</p>",
  "messages": [
    {
      "id": "755826",
      "postDate": "02/25/2020 06:35:53",
      "content": "<p><img src=\"https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F2716545%2F2a97fda2c91f68b3caadc42353f77fa4%2FWX20200225-143118.png?generation=1582612384525084&amp;alt=media\" alt=\"\">\nAfter clicking the submission button, it ran for about an hour smoothly, and here is the error called \"<strong>Exceeded allowed compute</strong>\", do you guys have any idea how to solve this kind of problem? Thanks in advance.</p>",
      "rawMarkdown": "![](https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F2716545%2F2a97fda2c91f68b3caadc42353f77fa4%2FWX20200225-143118.png?generation=1582612384525084&amp;alt=media)\nAfter clicking the submission button, it ran for about an hour smoothly, and here is the error called \"**Exceeded allowed compute**\", do you guys have any idea how to solve this kind of problem? Thanks in advance.",
      "votes": null
    },
    {
      "id": "755874",
      "postDate": "02/25/2020 08:08:53",
      "content": "<p>Try to speed up your pipeline. An hour of runtime for 400 samples is a bit longer then expected.</p>\n\n<p>It might be an automated check to prevent the platform from spending computational resources on running pipelines that would never succeed given the time restrictions.</p>",
      "rawMarkdown": "Try to speed up your pipeline. An hour of runtime for 400 samples is a bit longer then expected.\n\nIt might be an automated check to prevent the platform from spending computational resources on running pipelines that would never succeed given the time restrictions.",
      "votes": null
    },
    {
      "id": "756722",
      "postDate": "02/26/2020 02:25:27",
      "content": "<p>Thanks, An hour is for submitting rather than committing, it took about 20mins to commit the 400 sample dataset, I think it's a problem of memory leakage, I can run my scripts successfully in the local running environment with no memory leakage problem, does anyone have an idea about this?</p>",
      "rawMarkdown": "Thanks, An hour is for submitting rather than committing, it took about 20mins to commit the 400 sample dataset, I think it's a problem of memory leakage, I can run my scripts successfully in the local running environment with no memory leakage problem, does anyone have an idea about this?",
      "votes": null
    },
    {
      "id": "757059",
      "postDate": "02/26/2020 11:36:45",
      "content": "<p>Did you use up all your GPU for the week already?</p>",
      "rawMarkdown": "Did you use up all your GPU for the week already?",
      "votes": null
    },
    {
      "id": "757109",
      "postDate": "02/26/2020 12:53:10",
      "content": "<p>I still have more than 9 hours PGU quota when I submitted. BTW, thanks for your shared kernal, I actually modify based on yours. \nWhen I ran my scripts, I noticed the memory kept going up, it's ok when u have only 400 videos, but not for 4000 videos, out of memory.</p>",
      "rawMarkdown": "I still have more than 9 hours PGU quota when I submitted. BTW, thanks for your shared kernal, I actually modify based on yours. \nWhen I ran my scripts, I noticed the memory kept going up, it's ok when u have only 400 videos, but not for 4000 videos, out of memory.",
      "votes": null
    },
    {
      "id": "757691",
      "postDate": "02/27/2020 02:48:01",
      "content": "<p>I have the same problem. If Kaggle could just expose the the reason, Like which resource did we exceed, GPU memory, memory, HDD, whatever? It's extremely important.</p>",
      "rawMarkdown": "I have the same problem. If Kaggle could just expose the the reason, Like which resource did we exceed, GPU memory, memory, HDD, whatever? It's extremely important.",
      "votes": null
    },
    {
      "id": "757696",
      "postDate": "02/27/2020 02:55:08",
      "content": "<p>can't agree more, we need the exact error.</p>",
      "rawMarkdown": "can't agree more, we need the exact error.",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 755874,
      "author_name": "dvorobiev",
      "author_url": "",
      "post_date": "02/25/2020 08:08:53",
      "content": "<p>Try to speed up your pipeline. An hour of runtime for 400 samples is a bit longer then expected.</p>\n\n<p>It might be an automated check to prevent the platform from spending computational resources on running pipelines that would never succeed given the time restrictions.</p>",
      "votes": null,
      "replies": [
        {
          "id": 756722,
          "author_name": "dacianyu",
          "author_url": "",
          "post_date": "02/26/2020 02:25:27",
          "content": "<p>Thanks, An hour is for submitting rather than committing, it took about 20mins to commit the 400 sample dataset, I think it's a problem of memory leakage, I can run my scripts successfully in the local running environment with no memory leakage problem, does anyone have an idea about this?</p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 757059,
          "author_name": "humananalog",
          "author_url": "",
          "post_date": "02/26/2020 11:36:45",
          "content": "<p>Did you use up all your GPU for the week already?</p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 757109,
          "author_name": "dacianyu",
          "author_url": "",
          "post_date": "02/26/2020 12:53:10",
          "content": "<p>I still have more than 9 hours PGU quota when I submitted. BTW, thanks for your shared kernal, I actually modify based on yours. \nWhen I ran my scripts, I noticed the memory kept going up, it's ok when u have only 400 videos, but not for 4000 videos, out of memory.</p>",
          "votes": null,
          "replies": []
        }
      ]
    },
    {
      "id": 757691,
      "author_name": "am1to2",
      "author_url": "",
      "post_date": "02/27/2020 02:48:01",
      "content": "<p>I have the same problem. If Kaggle could just expose the the reason, Like which resource did we exceed, GPU memory, memory, HDD, whatever? It's extremely important.</p>",
      "votes": null,
      "replies": [
        {
          "id": 757696,
          "author_name": "dacianyu",
          "author_url": "",
          "post_date": "02/27/2020 02:55:08",
          "content": "<p>can't agree more, we need the exact error.</p>",
          "votes": null,
          "replies": []
        }
      ]
    }
  ],
  "raw_markdown_by_id": {
    "755826": "![](https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F2716545%2F2a97fda2c91f68b3caadc42353f77fa4%2FWX20200225-143118.png?generation=1582612384525084&amp;alt=media)\nAfter clicking the submission button, it ran for about an hour smoothly, and here is the error called \"**Exceeded allowed compute**\", do you guys have any idea how to solve this kind of problem? Thanks in advance.",
    "755874": "Try to speed up your pipeline. An hour of runtime for 400 samples is a bit longer then expected.\n\nIt might be an automated check to prevent the platform from spending computational resources on running pipelines that would never succeed given the time restrictions.",
    "756722": "Thanks, An hour is for submitting rather than committing, it took about 20mins to commit the 400 sample dataset, I think it's a problem of memory leakage, I can run my scripts successfully in the local running environment with no memory leakage problem, does anyone have an idea about this?",
    "757059": "Did you use up all your GPU for the week already?",
    "757109": "I still have more than 9 hours PGU quota when I submitted. BTW, thanks for your shared kernal, I actually modify based on yours. \nWhen I ran my scripts, I noticed the memory kept going up, it's ok when u have only 400 videos, but not for 4000 videos, out of memory.",
    "757691": "I have the same problem. If Kaggle could just expose the the reason, Like which resource did we exceed, GPU memory, memory, HDD, whatever? It's extremely important.",
    "757696": "can't agree more, we need the exact error."
  },
  "source": "meta"
}