{
  "id": 231850,
  "title": "Notebook Exceeded Allowed Compute",
  "url": "/competitions/coleridgeinitiative-show-us-the-data/discussion/231850",
  "author_name": "",
  "post_date": "2021-04-10T16:51:01.236805800Z",
  "votes": 3,
  "comment_count": 3,
  "views": 0,
  "content": "<p>I build a small RMarkdown -script to test input and output. Takes 9 sec to run. When I submit the submission.csv  I get an error after approx. 15 minutes : <br>\nNotebook Exceeded Allowed Compute<br>\nAny help ?</p>",
  "messages": [
    {
      "id": "1269566",
      "postDate": "04/10/2021 16:51:01",
      "content": "<p>I build a small RMarkdown -script to test input and output. Takes 9 sec to run. When I submit the submission.csv  I get an error after approx. 15 minutes : <br>\nNotebook Exceeded Allowed Compute<br>\nAny help ?</p>",
      "rawMarkdown": "I build a small RMarkdown -script to test input and output. Takes 9 sec to run. When I submit the submission.csv  I get an error after approx. 15 minutes : \nNotebook Exceeded Allowed Compute\nAny help ?",
      "votes": null
    },
    {
      "id": "1270929",
      "postDate": "04/12/2021 07:02:18",
      "content": "<p>Hi <a href=\"https://www.kaggle.com/pehahn\" target=\"_blank\">@pehahn</a> ,<br>\nYou can follow <a href=\"https://www.kaggle.com/code-competition-debugging\" target=\"_blank\">this</a> link to debug the error codes in Code competitions.  </p>\n<p>According to the documentation, your error is defined as:-<br>\n<code>Notebook Exceeded Allowed Compute: This indicates you have violated a code requirement constraint during the rerun. This includes limitations in the execution environment, for example requesting more RAM or disk than available, or competition constraints, such as input data source type or size limits.</code></p>",
      "rawMarkdown": "Hi @pehahn ,\nYou can follow [this](https://www.kaggle.com/code-competition-debugging) link to debug the error codes in Code competitions.  \n\nAccording to the documentation, your error is defined as:-\n`Notebook Exceeded Allowed Compute: This indicates you have violated a code requirement constraint during the rerun. This includes limitations in the execution environment, for example requesting more RAM or disk than available, or competition constraints, such as input data source type or size limits.`",
      "votes": null
    },
    {
      "id": "1271589",
      "postDate": "04/12/2021 18:05:11",
      "content": "<p>Thank you. Very difficult. I believe that my input and my calculation are very small. </p>",
      "rawMarkdown": "Thank you. Very difficult. I believe that my input and my calculation are very small.",
      "votes": null
    },
    {
      "id": "1271599",
      "postDate": "04/12/2021 18:16:01",
      "content": "<p>Hi <a href=\"https://www.kaggle.com/pehahn\" target=\"_blank\">@pehahn</a> ,<br>\nBut you also have to factor in the fact that there is also a hidden test set on which your Kernel is being run. Because of the small size of public test set, it might not create a problem while testing, but when you submit for evaluation it might cause hardware limitation problems depending on the scalability of your solution.<br>\nAnother brute way might be to reduce batch sized while inferencing as low as you can go and see if it raises the same issue. If it still does, then there is a fundamental challenge in your approach. And if it doesn't it means that the size(and in extension the RAM) was the issue.<br>\nHope it helps! 😊</p>",
      "rawMarkdown": "Hi @pehahn ,\nBut you also have to factor in the fact that there is also a hidden test set on which your Kernel is being run. Because of the small size of public test set, it might not create a problem while testing, but when you submit for evaluation it might cause hardware limitation problems depending on the scalability of your solution.\nAnother brute way might be to reduce batch sized while inferencing as low as you can go and see if it raises the same issue. If it still does, then there is a fundamental challenge in your approach. And if it doesn't it means that the size(and in extension the RAM) was the issue.\nHope it helps! 😊",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 1270929,
      "author_name": "manabendrarout",
      "author_url": "",
      "post_date": "04/12/2021 07:02:18",
      "content": "<p>Hi <a href=\"https://www.kaggle.com/pehahn\" target=\"_blank\">@pehahn</a> ,<br>\nYou can follow <a href=\"https://www.kaggle.com/code-competition-debugging\" target=\"_blank\">this</a> link to debug the error codes in Code competitions.  </p>\n<p>According to the documentation, your error is defined as:-<br>\n<code>Notebook Exceeded Allowed Compute: This indicates you have violated a code requirement constraint during the rerun. This includes limitations in the execution environment, for example requesting more RAM or disk than available, or competition constraints, such as input data source type or size limits.</code></p>",
      "votes": null,
      "replies": [
        {
          "id": 1271589,
          "author_name": "pehahn",
          "author_url": "",
          "post_date": "04/12/2021 18:05:11",
          "content": "<p>Thank you. Very difficult. I believe that my input and my calculation are very small. </p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 1271599,
          "author_name": "manabendrarout",
          "author_url": "",
          "post_date": "04/12/2021 18:16:01",
          "content": "<p>Hi <a href=\"https://www.kaggle.com/pehahn\" target=\"_blank\">@pehahn</a> ,<br>\nBut you also have to factor in the fact that there is also a hidden test set on which your Kernel is being run. Because of the small size of public test set, it might not create a problem while testing, but when you submit for evaluation it might cause hardware limitation problems depending on the scalability of your solution.<br>\nAnother brute way might be to reduce batch sized while inferencing as low as you can go and see if it raises the same issue. If it still does, then there is a fundamental challenge in your approach. And if it doesn't it means that the size(and in extension the RAM) was the issue.<br>\nHope it helps! 😊</p>",
          "votes": null,
          "replies": []
        }
      ]
    }
  ],
  "raw_markdown_by_id": {
    "1269566": "I build a small RMarkdown -script to test input and output. Takes 9 sec to run. When I submit the submission.csv  I get an error after approx. 15 minutes : \nNotebook Exceeded Allowed Compute\nAny help ?",
    "1270929": "Hi @pehahn ,\nYou can follow [this](https://www.kaggle.com/code-competition-debugging) link to debug the error codes in Code competitions.  \n\nAccording to the documentation, your error is defined as:-\n`Notebook Exceeded Allowed Compute: This indicates you have violated a code requirement constraint during the rerun. This includes limitations in the execution environment, for example requesting more RAM or disk than available, or competition constraints, such as input data source type or size limits.`",
    "1271589": "Thank you. Very difficult. I believe that my input and my calculation are very small.",
    "1271599": "Hi @pehahn ,\nBut you also have to factor in the fact that there is also a hidden test set on which your Kernel is being run. Because of the small size of public test set, it might not create a problem while testing, but when you submit for evaluation it might cause hardware limitation problems depending on the scalability of your solution.\nAnother brute way might be to reduce batch sized while inferencing as low as you can go and see if it raises the same issue. If it still does, then there is a fundamental challenge in your approach. And if it doesn't it means that the size(and in extension the RAM) was the issue.\nHope it helps! 😊"
  },
  "source": "meta"
}