{
  "id": 55129,
  "title": "What is the kernel execution time constraint?",
  "url": "/competitions/talkingdata-adtracking-fraud-detection/discussion/55129",
  "author_name": "",
  "post_date": "2018-04-22T15:10:33.278593Z",
  "votes": 1,
  "comment_count": 9,
  "views": 0,
  "content": "<p>I am sure I read that information over but I am not really sure what the kernel execution time constraint is within this competition? \nIn other competitions it was 1 hour but within this one the execution stops at some strange times. \nThanks!</p>",
  "messages": [
    {
      "id": "317789",
      "postDate": "04/22/2018 15:10:33",
      "content": "<p>I am sure I read that information over but I am not really sure what the kernel execution time constraint is within this competition? \nIn other competitions it was 1 hour but within this one the execution stops at some strange times. \nThanks!</p>",
      "rawMarkdown": "I am sure I read that information over but I am not really sure what the kernel execution time constraint is within this competition? \nIn other competitions it was 1 hour but within this one the execution stops at some strange times. \nThanks!",
      "votes": null
    },
    {
      "id": "317790",
      "postDate": "04/22/2018 15:12:30",
      "content": "<p>also 1 hour</p>",
      "rawMarkdown": "also 1 hour",
      "votes": null
    },
    {
      "id": "317793",
      "postDate": "04/22/2018 15:17:15",
      "content": "<p>I believe that at least for this competition execution time is now up to 6 hours, and certainly more than 1 hour. If you're seeing unexpected interruptions in execution that aren't explained by code errors, it's probable that you're encountering memory errors instead (you're limited to 16GB of RAM, and this data is large). </p>\n\n<p>Edit: the memory error code is 137, so if you see that you know for sure (\"exited with code 137\").</p>",
      "rawMarkdown": "I believe that at least for this competition execution time is now up to 6 hours, and certainly more than 1 hour. If you're seeing unexpected interruptions in execution that aren't explained by code errors, it's probable that you're encountering memory errors instead (you're limited to 16GB of RAM, and this data is large). \n\nEdit: the memory error code is 137, so if you see that you know for sure (\"exited with code 137\").",
      "votes": null
    },
    {
      "id": "317806",
      "postDate": "04/22/2018 15:37:32",
      "content": "<p>I've got \"The kernel was killed for running longer than 3600 seconds.\" error yesterday.</p>",
      "rawMarkdown": "I've got \"The kernel was killed for running longer than 3600 seconds.\" error yesterday.",
      "votes": null
    },
    {
      "id": "317813",
      "postDate": "04/22/2018 15:53:02",
      "content": "<p>I think 1 hour used to be kernel runtime limit but this was increased to 6 hrs recently... I think its just before this competition started....</p>",
      "rawMarkdown": "I think 1 hour used to be kernel runtime limit but this was increased to 6 hrs recently... I think its just before this competition started....",
      "votes": null
    },
    {
      "id": "317814",
      "postDate": "04/22/2018 15:53:26",
      "content": "<p>Likely a bug. If you look at some of the public kernels you can see execution times well in excess of 3600 seconds.</p>",
      "rawMarkdown": "Likely a bug. If you look at some of the public kernels you can see execution times well in excess of 3600 seconds.",
      "votes": null
    },
    {
      "id": "317836",
      "postDate": "04/22/2018 17:06:31",
      "content": "<p>Is there any official statement on that? I see aborts for 1 hour (not for mem limit) and aborts for much longer durations. It would be good to know the hard limit before the competition ends...</p>",
      "rawMarkdown": "Is there any official statement on that? I see aborts for 1 hour (not for mem limit) and aborts for much longer durations. It would be good to know the hard limit before the competition ends...",
      "votes": null
    },
    {
      "id": "317850",
      "postDate": "04/22/2018 17:24:08",
      "content": "<p>There you go - <a href=\"https://www.kaggle.com/product-feedback/52499\">https://www.kaggle.com/product-feedback/52499</a></p>",
      "rawMarkdown": "There you go - https://www.kaggle.com/product-feedback/52499",
      "votes": null
    },
    {
      "id": "317851",
      "postDate": "04/22/2018 17:26:19",
      "content": "<p>Personally I just saw one of my long running scripts and it completed successfully in approx 20000 seconds ~ 5.5 hrs..</p>",
      "rawMarkdown": "Personally I just saw one of my long running scripts and it completed successfully in approx 20000 seconds ~ 5.5 hrs..",
      "votes": null
    },
    {
      "id": "318001",
      "postDate": "04/23/2018 02:49:26",
      "content": "<p>Very cool, many thanks!</p>",
      "rawMarkdown": "Very cool, many thanks!",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 317790,
      "author_name": "geron82",
      "author_url": "",
      "post_date": "04/22/2018 15:12:30",
      "content": "<p>also 1 hour</p>",
      "votes": null,
      "replies": []
    },
    {
      "id": 317793,
      "author_name": "aquatic",
      "author_url": "",
      "post_date": "04/22/2018 15:17:15",
      "content": "<p>I believe that at least for this competition execution time is now up to 6 hours, and certainly more than 1 hour. If you're seeing unexpected interruptions in execution that aren't explained by code errors, it's probable that you're encountering memory errors instead (you're limited to 16GB of RAM, and this data is large). </p>\n\n<p>Edit: the memory error code is 137, so if you see that you know for sure (\"exited with code 137\").</p>",
      "votes": null,
      "replies": []
    },
    {
      "id": 317806,
      "author_name": "geron82",
      "author_url": "",
      "post_date": "04/22/2018 15:37:32",
      "content": "<p>I've got \"The kernel was killed for running longer than 3600 seconds.\" error yesterday.</p>",
      "votes": null,
      "replies": [
        {
          "id": 317814,
          "author_name": "aquatic",
          "author_url": "",
          "post_date": "04/22/2018 15:53:26",
          "content": "<p>Likely a bug. If you look at some of the public kernels you can see execution times well in excess of 3600 seconds.</p>",
          "votes": null,
          "replies": []
        }
      ]
    },
    {
      "id": 317813,
      "author_name": "samratp",
      "author_url": "",
      "post_date": "04/22/2018 15:53:02",
      "content": "<p>I think 1 hour used to be kernel runtime limit but this was increased to 6 hrs recently... I think its just before this competition started....</p>",
      "votes": null,
      "replies": []
    },
    {
      "id": 317836,
      "author_name": "wolfgangb33r",
      "author_url": "",
      "post_date": "04/22/2018 17:06:31",
      "content": "<p>Is there any official statement on that? I see aborts for 1 hour (not for mem limit) and aborts for much longer durations. It would be good to know the hard limit before the competition ends...</p>",
      "votes": null,
      "replies": [
        {
          "id": 317850,
          "author_name": "samratp",
          "author_url": "",
          "post_date": "04/22/2018 17:24:08",
          "content": "<p>There you go - <a href=\"https://www.kaggle.com/product-feedback/52499\">https://www.kaggle.com/product-feedback/52499</a></p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 317851,
          "author_name": "samratp",
          "author_url": "",
          "post_date": "04/22/2018 17:26:19",
          "content": "<p>Personally I just saw one of my long running scripts and it completed successfully in approx 20000 seconds ~ 5.5 hrs..</p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 318001,
          "author_name": "wolfgangb33r",
          "author_url": "",
          "post_date": "04/23/2018 02:49:26",
          "content": "<p>Very cool, many thanks!</p>",
          "votes": null,
          "replies": []
        }
      ]
    }
  ],
  "raw_markdown_by_id": {
    "317789": "I am sure I read that information over but I am not really sure what the kernel execution time constraint is within this competition? \nIn other competitions it was 1 hour but within this one the execution stops at some strange times. \nThanks!",
    "317790": "also 1 hour",
    "317793": "I believe that at least for this competition execution time is now up to 6 hours, and certainly more than 1 hour. If you're seeing unexpected interruptions in execution that aren't explained by code errors, it's probable that you're encountering memory errors instead (you're limited to 16GB of RAM, and this data is large). \n\nEdit: the memory error code is 137, so if you see that you know for sure (\"exited with code 137\").",
    "317806": "I've got \"The kernel was killed for running longer than 3600 seconds.\" error yesterday.",
    "317813": "I think 1 hour used to be kernel runtime limit but this was increased to 6 hrs recently... I think its just before this competition started....",
    "317814": "Likely a bug. If you look at some of the public kernels you can see execution times well in excess of 3600 seconds.",
    "317836": "Is there any official statement on that? I see aborts for 1 hour (not for mem limit) and aborts for much longer durations. It would be good to know the hard limit before the competition ends...",
    "317850": "There you go - https://www.kaggle.com/product-feedback/52499",
    "317851": "Personally I just saw one of my long running scripts and it completed successfully in approx 20000 seconds ~ 5.5 hrs..",
    "318001": "Very cool, many thanks!"
  },
  "source": "meta"
}