{
  "id": 105564,
  "title": "Quick work around on \"Interactive GPU=1 session\"",
  "url": "/competitions/aptos2019-blindness-detection/discussion/105564",
  "author_name": "",
  "post_date": "2019-08-24T06:34:24.238005200Z",
  "votes": 11,
  "comment_count": 1,
  "views": 0,
  "content": "<p>Hi just a small note to many of us who have a problem with the  maximum \"interactive=1\" session.</p>\n\n<p>In case that we just want to program and save (commit), we can switch GPU=OFF, the current limit of \"cpu-only\" is 10. Therefore, we can still edit many kernels at the same time.</p>\n\n<p>If you want to close the interactive GPU session, take a look at top-right corner in the screen. There, you can stop the current active one.</p>",
  "messages": [
    {
      "id": "606831",
      "postDate": "08/24/2019 06:34:24",
      "content": "<p>Hi just a small note to many of us who have a problem with the  maximum \"interactive=1\" session.</p>\n\n<p>In case that we just want to program and save (commit), we can switch GPU=OFF, the current limit of \"cpu-only\" is 10. Therefore, we can still edit many kernels at the same time.</p>\n\n<p>If you want to close the interactive GPU session, take a look at top-right corner in the screen. There, you can stop the current active one.</p>",
      "rawMarkdown": "Hi just a small note to many of us who have a problem with the  maximum \"interactive=1\" session.\n\nIn case that we just want to program and save (commit), we can switch GPU=OFF, the current limit of \"cpu-only\" is 10. Therefore, we can still edit many kernels at the same time.\n\nIf you want to close the interactive GPU session, take a look at top-right corner in the screen. There, you can stop the current active one.",
      "votes": null
    },
    {
      "id": "607446",
      "postDate": "08/25/2019 09:07:16",
      "content": "<p>Kaggle is becoming more and more unfriendly to players who lack GPU. In the sprint phase towards the end of the competition, we cannot get enough GPU resources to do the final experiments and tests.</p>",
      "rawMarkdown": "Kaggle is becoming more and more unfriendly to players who lack GPU. In the sprint phase towards the end of the competition, we cannot get enough GPU resources to do the final experiments and tests.",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 607446,
      "author_name": "seefun",
      "author_url": "",
      "post_date": "08/25/2019 09:07:16",
      "content": "<p>Kaggle is becoming more and more unfriendly to players who lack GPU. In the sprint phase towards the end of the competition, we cannot get enough GPU resources to do the final experiments and tests.</p>",
      "votes": null,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "606831": "Hi just a small note to many of us who have a problem with the  maximum \"interactive=1\" session.\n\nIn case that we just want to program and save (commit), we can switch GPU=OFF, the current limit of \"cpu-only\" is 10. Therefore, we can still edit many kernels at the same time.\n\nIf you want to close the interactive GPU session, take a look at top-right corner in the screen. There, you can stop the current active one.",
    "607446": "Kaggle is becoming more and more unfriendly to players who lack GPU. In the sprint phase towards the end of the competition, we cannot get enough GPU resources to do the final experiments and tests."
  },
  "source": "meta"
}