{
  "competition": "rsna-knee-abnormality-detection",
  "topic_id": "739000",
  "comments": [
    {
      "id": 3519981,
      "authorName": "Linda PerezP",
      "votes": 1,
      "postDate": "2026-09-02T16:10:17.490000",
      "content": "<p>Hi Fran, </p>\n<p>You can use Kaggle, AWS, GCP and even your local computer without GPUs. Take into account, the time, complexity and cost associated to the project. Ask your LLM, what are the Data Engineering and Deployment aspects that you should cover for a multimodal project like this provide the Competition link. </p>\n<p>Good Luck! </p>"
    },
    {
      "id": 3519966,
      "authorName": "Dread Development",
      "votes": 1,
      "postDate": "2026-09-02T15:42:34.967000",
      "content": "<p>Yes you absolutely can! If you’re looking for cheap options outside of your own local GPU’s vast.ai is what I generally use</p>"
    },
    {
      "id": 3520261,
      "authorName": "Phuc",
      "votes": 1,
      "postDate": "2026-09-03T03:02:19.480000",
      "content": "<p>Hi, How can you transfer data between and within new instances in Vastai? I wonder if anyone can use spot instances effectively.</p>"
    },
    {
      "id": 3520270,
      "authorName": "Dread Development",
      "votes": 1,
      "postDate": "2026-09-03T03:15:25.847000",
      "content": "<p>Hey! So I treat vast as disposable compute, not storage so small files &amp; code go directly over SSH with scp on Linux\nrsync -avP is better because interrupted transfers resume.\nFor large datasets, upload them once to a persistent storage like a vast volume, S3 etc then let every new instance pull from there instead of uploading repeatedly.\nI do use the spot instances with little to no issue ever, you just have to make sure you're monitoring &amp; saving checkpoints.\nI have also found that chunking &amp; sending parallel transfers is much more effective for large files.\nI have used the spot instances for a number of comps as well as my own distillation, pre training &amp; fine tuning with less issues than I have finger so, hope this helped!\nIf you have any more questions feel free!</p>"
    },
    {
      "id": 3519946,
      "authorName": "Seung Sup Lee",
      "votes": 1,
      "postDate": "2026-09-02T14:48:27.377000",
      "content": "<p>Yes, you can train on your own GPU.</p>\n<p>You can set up Ubuntu locally with Python, PyTorch, CUDA, and the libraries you need, then do most of your training there.</p>\n<p>If you are starting now, I recommend targeting Kaggle’s <strong>Tesla T4 x2</strong> environment rather than the P100, since the P100 is being retired.</p>\n<p>One important thing: each T4 has <strong>16 GB of VRAM</strong>. T4 x2 means two separate 16 GB GPUs, not one 32 GB GPU.</p>\n<p>For a beginner, I strongly recommend starting with <strong>one GPU first</strong>. Make sure the whole training or inference pipeline finishes correctly within 16 GB VRAM. Once that works reliably, then modify the code to use both T4 GPUs in parallel.</p>\n<p>Multi-GPU code adds extra complexity, so debugging is much easier if the single-GPU version already works.</p>\n<p>Also, if your local GPU has much more VRAM, your code may work locally but fail on Kaggle. You may need to reduce the batch size, input size, model size, or memory usage before uploading it.</p>\n<p>So the safest approach is:</p>\n<p><strong>Local Ubuntu → one GPU → fit within 16 GB VRAM → complete the full pipeline → then optimize for T4 x2.</strong></p>"
    },
    {
      "id": 3520177,
      "authorName": "fran garcia",
      "votes": 0,
      "postDate": "2026-09-02T23:13:51.507000",
      "content": "<p>Thanks! I have another question. If I train locally, do I have to download the Kaggle dataset?</p>"
    },
    {
      "id": 3520229,
      "authorName": "PC Jimmmy",
      "votes": 1,
      "postDate": "2026-09-03T02:14:02.927000",
      "content": "<p>Yes - you need to download the kaggle data.  </p>"
    },
    {
      "id": 3520295,
      "authorName": "Komil Parmar",
      "votes": 1,
      "postDate": "2026-09-03T04:59:48.167000",
      "content": "<p>I don't understand this question. If you want to train locally, why or how wouldn't you need to have the data locally as well? \nAre you planning to make some data stream? Or train a model without using the competition data?</p>"
    },
    {
      "id": 3520883,
      "authorName": "Seung Sup Lee",
      "votes": 1,
      "postDate": "2026-09-04T11:08:05.673000",
      "content": "<p>Yes. If you want to work on it locally, you need to download the competition data to your PC. In my case, the compressed ZIP file is about 247 GB, and downloading such a large file from overseas can be quite slow and inconvenient.</p>\n<p>Kaggle also appears to be using Google-hosted infrastructure, and from what I have observed, the server location may differ depending on the runtime. For example, CPU-only sessions and Tesla T4 ×2 GPU sessions seem to be assigned to different server regions within the United States. This may also affect download and transfer speeds for overseas participants.</p>"
    },
    {
      "id": 3519905,
      "authorName": "PC Jimmmy",
      "votes": 1,
      "postDate": "2026-09-02T12:56:16.383000",
      "content": "<p>You can use your GPU's, if your a relative of Elon Musk maybe he would let you use the Nashville facility.</p>\n<p>Almost 100% of kaggle competitions let you train local.  You will need to attached your model files in a data set, but lots of examples of how to do that and most LLM's know enough about kaggle to help you create a zip file local to use in the data set.</p>\n<p>Only the final inference and creation of the submission.csv needs to be on a kaggle notebook.</p>\n<p>have fun</p>"
    },
    {
      "id": 3522093,
      "authorName": "Moonwon12",
      "votes": -1,
      "postDate": "2026-09-08T04:52:14.360000",
      "content": "<p>Hi! I'm also new to kaggle and this is my first competition.\nI think you can use your own GPU but it is not recomended. I don't know your GPU availablity but for me 30h capcity that kaggle support was enough.</p>"
    }
  ],
  "messages": [],
  "raw_show": {
    "topic": {
      "id": 739000,
      "title": "Working with our own GPU",
      "authorName": "fran garcia",
      "commentCount": 11,
      "votes": 1,
      "postDate": "2026-09-02T12:33:53.103000"
    },
    "comments": [
      {
        "id": 3519981,
        "authorName": "Linda PerezP",
        "votes": 1,
        "postDate": "2026-09-02T16:10:17.490000",
        "content": "<p>Hi Fran, </p>\n<p>You can use Kaggle, AWS, GCP and even your local computer without GPUs. Take into account, the time, complexity and cost associated to the project. Ask your LLM, what are the Data Engineering and Deployment aspects that you should cover for a multimodal project like this provide the Competition link. </p>\n<p>Good Luck! </p>"
      },
      {
        "id": 3519966,
        "authorName": "Dread Development",
        "votes": 1,
        "postDate": "2026-09-02T15:42:34.967000",
        "content": "<p>Yes you absolutely can! If you’re looking for cheap options outside of your own local GPU’s vast.ai is what I generally use</p>"
      },
      {
        "id": 3520261,
        "authorName": "Phuc",
        "votes": 1,
        "postDate": "2026-09-03T03:02:19.480000",
        "content": "<p>Hi, How can you transfer data between and within new instances in Vastai? I wonder if anyone can use spot instances effectively.</p>"
      },
      {
        "id": 3520270,
        "authorName": "Dread Development",
        "votes": 1,
        "postDate": "2026-09-03T03:15:25.847000",
        "content": "<p>Hey! So I treat vast as disposable compute, not storage so small files &amp; code go directly over SSH with scp on Linux\nrsync -avP is better because interrupted transfers resume.\nFor large datasets, upload them once to a persistent storage like a vast volume, S3 etc then let every new instance pull from there instead of uploading repeatedly.\nI do use the spot instances with little to no issue ever, you just have to make sure you're monitoring &amp; saving checkpoints.\nI have also found that chunking &amp; sending parallel transfers is much more effective for large files.\nI have used the spot instances for a number of comps as well as my own distillation, pre training &amp; fine tuning with less issues than I have finger so, hope this helped!\nIf you have any more questions feel free!</p>"
      },
      {
        "id": 3519946,
        "authorName": "Seung Sup Lee",
        "votes": 1,
        "postDate": "2026-09-02T14:48:27.377000",
        "content": "<p>Yes, you can train on your own GPU.</p>\n<p>You can set up Ubuntu locally with Python, PyTorch, CUDA, and the libraries you need, then do most of your training there.</p>\n<p>If you are starting now, I recommend targeting Kaggle’s <strong>Tesla T4 x2</strong> environment rather than the P100, since the P100 is being retired.</p>\n<p>One important thing: each T4 has <strong>16 GB of VRAM</strong>. T4 x2 means two separate 16 GB GPUs, not one 32 GB GPU.</p>\n<p>For a beginner, I strongly recommend starting with <strong>one GPU first</strong>. Make sure the whole training or inference pipeline finishes correctly within 16 GB VRAM. Once that works reliably, then modify the code to use both T4 GPUs in parallel.</p>\n<p>Multi-GPU code adds extra complexity, so debugging is much easier if the single-GPU version already works.</p>\n<p>Also, if your local GPU has much more VRAM, your code may work locally but fail on Kaggle. You may need to reduce the batch size, input size, model size, or memory usage before uploading it.</p>\n<p>So the safest approach is:</p>\n<p><strong>Local Ubuntu → one GPU → fit within 16 GB VRAM → complete the full pipeline → then optimize for T4 x2.</strong></p>"
      },
      {
        "id": 3520177,
        "authorName": "fran garcia",
        "votes": 0,
        "postDate": "2026-09-02T23:13:51.507000",
        "content": "<p>Thanks! I have another question. If I train locally, do I have to download the Kaggle dataset?</p>"
      },
      {
        "id": 3520229,
        "authorName": "PC Jimmmy",
        "votes": 1,
        "postDate": "2026-09-03T02:14:02.927000",
        "content": "<p>Yes - you need to download the kaggle data.  </p>"
      },
      {
        "id": 3520295,
        "authorName": "Komil Parmar",
        "votes": 1,
        "postDate": "2026-09-03T04:59:48.167000",
        "content": "<p>I don't understand this question. If you want to train locally, why or how wouldn't you need to have the data locally as well? \nAre you planning to make some data stream? Or train a model without using the competition data?</p>"
      },
      {
        "id": 3520883,
        "authorName": "Seung Sup Lee",
        "votes": 1,
        "postDate": "2026-09-04T11:08:05.673000",
        "content": "<p>Yes. If you want to work on it locally, you need to download the competition data to your PC. In my case, the compressed ZIP file is about 247 GB, and downloading such a large file from overseas can be quite slow and inconvenient.</p>\n<p>Kaggle also appears to be using Google-hosted infrastructure, and from what I have observed, the server location may differ depending on the runtime. For example, CPU-only sessions and Tesla T4 ×2 GPU sessions seem to be assigned to different server regions within the United States. This may also affect download and transfer speeds for overseas participants.</p>"
      },
      {
        "id": 3519905,
        "authorName": "PC Jimmmy",
        "votes": 1,
        "postDate": "2026-09-02T12:56:16.383000",
        "content": "<p>You can use your GPU's, if your a relative of Elon Musk maybe he would let you use the Nashville facility.</p>\n<p>Almost 100% of kaggle competitions let you train local.  You will need to attached your model files in a data set, but lots of examples of how to do that and most LLM's know enough about kaggle to help you create a zip file local to use in the data set.</p>\n<p>Only the final inference and creation of the submission.csv needs to be on a kaggle notebook.</p>\n<p>have fun</p>"
      },
      {
        "id": 3522093,
        "authorName": "Moonwon12",
        "votes": -1,
        "postDate": "2026-09-08T04:52:14.360000",
        "content": "<p>Hi! I'm also new to kaggle and this is my first competition.\nI think you can use your own GPU but it is not recomended. I don't know your GPU availablity but for me 30h capcity that kaggle support was enough.</p>"
      }
    ]
  },
  "topic": {
    "id": 739000,
    "title": "Working with our own GPU",
    "authorName": "fran garcia",
    "commentCount": 11,
    "votes": 1,
    "postDate": "2026-09-02T12:33:53.103000"
  },
  "index": {
    "id": "739000",
    "title": "Working with our own GPU",
    "authorName": "",
    "commentCount": "11",
    "votes": "1",
    "postDate": "2026-09-02 12:33:53.103000"
  }
}