{
  "id": 357011,
  "title": "Notebook timeout",
  "url": "/competitions/rsna-2022-cervical-spine-fracture-detection/discussion/357011",
  "author_name": "Samuel Cortinhas",
  "post_date": "2022-10-02T22:56:33.360000",
  "votes": 4,
  "comment_count": 2,
  "views": 0,
  "content": "<p>My training notebook took 9.5 hours to run. I re-ran the notebook with a smaller learning rate (same number of epochs/steps) but the notebook timed out after 12 hours. Is it Kaggle hardware or PyTorch being weird?</p>",
  "messages": [
    {
      "id": 1968143,
      "postDate": "2022-10-02T22:56:33.360Z",
      "content": "<p>My training notebook took 9.5 hours to run. I re-ran the notebook with a smaller learning rate (same number of epochs/steps) but the notebook timed out after 12 hours. Is it Kaggle hardware or PyTorch being weird?</p>",
      "rawMarkdown": "My training notebook took 9.5 hours to run. I re-ran the notebook with a smaller learning rate (same number of epochs/steps) but the notebook timed out after 12 hours. Is it Kaggle hardware or PyTorch being weird?",
      "votes": 4
    },
    {
      "id": 1976125,
      "postDate": "2022-10-07T07:07:45.593Z",
      "content": "<p>It happened to me too when I tried to run a \"end-to-end\" notebook with model training in it for submission. right now I'm trying just to do inference in the kaggle notebook and hope that it will not time out this time</p>",
      "rawMarkdown": "It happened to me too when I tried to run a \"end-to-end\" notebook with model training in it for submission. right now I'm trying just to do inference in the kaggle notebook and hope that it will not time out this time",
      "votes": 1
    },
    {
      "id": 1968153,
      "postDate": "2022-10-02T23:18:08.267Z",
      "content": "<p>Although I don't use kaggle notebooks, I see pytorch being weird sometimes on my local machine, and now that you mention it, it does happen more when I try to change the learning rate, a restart fix this for me.</p>",
      "rawMarkdown": "Although I don't use kaggle notebooks, I see pytorch being weird sometimes on my local machine, and now that you mention it, it does happen more when I try to change the learning rate, a restart fix this for me.",
      "votes": 1
    }
  ],
  "comments": [
    {
      "id": 1976125,
      "author_name": "Marius ",
      "author_url": "",
      "post_date": "2022-10-07T07:07:45.593000",
      "content": "<p>It happened to me too when I tried to run a \"end-to-end\" notebook with model training in it for submission. right now I'm trying just to do inference in the kaggle notebook and hope that it will not time out this time</p>",
      "votes": 1,
      "replies": []
    },
    {
      "id": 1968153,
      "author_name": "Harshit Sheoran",
      "author_url": "",
      "post_date": "2022-10-02T23:18:08.267000",
      "content": "<p>Although I don't use kaggle notebooks, I see pytorch being weird sometimes on my local machine, and now that you mention it, it does happen more when I try to change the learning rate, a restart fix this for me.</p>",
      "votes": 1,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "1968143": "My training notebook took 9.5 hours to run. I re-ran the notebook with a smaller learning rate (same number of epochs/steps) but the notebook timed out after 12 hours. Is it Kaggle hardware or PyTorch being weird?",
    "1976125": "It happened to me too when I tried to run a \"end-to-end\" notebook with model training in it for submission. right now I'm trying just to do inference in the kaggle notebook and hope that it will not time out this time",
    "1968153": "Although I don't use kaggle notebooks, I see pytorch being weird sometimes on my local machine, and now that you mention it, it does happen more when I try to change the learning rate, a restart fix this for me."
  }
}