Skip to content
TheChatArchiveThe Chat Archive
Claudeclaude-opus-4-20250514· AnthropicHugging Face LMArena Human Preference 140K

Do most people just use a 512 GB disk or SSD?

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Geminigemini-2.5-flash’s answer.
  1. User

    Do most people just use a 512 GB disk or SSD?

  2. Claude Assistant

    Yes, 512 GB is probably the most common "sweet spot" for desktop/laptop users today, especially for SSDs. Here's why:

    Current market trends:

    • 256 GB: Often feels cramped once you add a few games, development environments, or virtual machines
    • 512 GB: The mainstream choice - enough for OS, apps, documents, and some media without constant space management
    • 1 TB+: Popular with power users, gamers, content creators, or anyone who wants to "set it and forget it"

    For an Arch Linux setup specifically: With a 512 GB drive, you'd typically have:

    • 20-50 GB for / (root)
    • 450-480 GB for /home
    • Maybe 8-16 GB for swap

    This gives you tons of room for:

    • Multiple desktop environments to experiment with
    • Development tools, containers, VMs
    • Moderate gaming library
    • Some local media files
    • AUR build caches
    • System snapshots/backups

    Price considerations: 512 GB SSDs hit the best price/capacity ratio right now. The jump from 256 GB → 512 GB is usually modest in cost, while 512 GB → 1 TB often doubles the price.

    So yes, if you're buying today and don't have specific high-storage needs (video editing, huge game libraries, data hoarding), 512 GB is the sensible default choice for most Linux users.

  3. User

    if I'm partitioning a drive, and can choose any partition size I want for the OS, leaving the rest for data on a different partition on the same drive, how does 320 GB sound for the OS partition, leaving the rest for data and possibly a swap partition? (Or should I forget a swap partition and just use a swap file if I ever chose to enable hibernation, as this leaves more room for data?)

  4. Claude Assistant

    320 GB for the OS partition is way more than you'll ever need for Arch + applications. You're essentially allocating 10x what's necessary, which wastes space that could be used for your data partition.

    Better allocation would be:

    • OS partition (/): 50-80 GB - This is already very generous for Arch
    • Data partition (/home): Everything else minus swap
    • Swap: Use a swapfile instead of partition

    Why 50-80 GB is plenty:

    • Covers all desktop apps, development tools, containers
    • Leaves room for package caches, logs, temporary builds
    • Allows installing multiple DEs if you want to experiment
    • Still has 20-30 GB of breathing room

    Swap file vs partition: Definitely go with a swap file:

    • Just as fast as a swap partition on modern systems
    • Can resize/delete easily without repartitioning
    • Only takes space when you create it
    • Works perfectly for hibernation

    Example for a 512 GB drive:

    /boot/efi: 512 MB (if UEFI)
    /: 60 GB
    /home: ~451 GB
    Swapfile: Create later in /home if needed
    

    This gives you 7-8x more usable space for your actual files while still having a very comfortable OS partition. Unless you're planning something unusual (like hosting 50+ Docker containers or keeping years of system logs), anything over 80 GB for / is just wasted space.

  5. User

    what if it is a large drive, like a 2TB drive?

  6. Claude Assistant

    Even with a 2TB drive, I'd still recommend keeping the OS partition modest - there's no benefit to making it huge just because you have the space.

    Recommended for 2TB drive:

    • OS partition (/): 80-100 GB - Still more than enough
    • Data partition (/home): ~1.9 TB
    • Swap: Swapfile as needed

    Why not go bigger on OS?

    • Arch + apps simply won't use it - even with every DE installed, tons of development tools, containers, etc., you'd struggle to fill 100 GB
    • Smaller partitions are faster to backup/restore
    • Easier to manage snapshots if you use btrfs/timeshift
    • Keeps your system files separate from data

    The only reasons to go bigger:

    • Planning to store lots of VMs/containers in /var
    • Want to keep massive AUR build caches forever
    • Running services that generate huge logs
    • Planning some unusual server-like setup

    Example partition layout:

    /boot/efi: 512 MB
    /: 100 GB (very generous)
    /home: 1.9+ TB
    

    Think of it this way: Would you build a 10-car garage just because you have the land, when you only own 2 cars? The extra space in / just sits empty forever. Better to allocate it where you'll actually use it - in /home for your files, projects, media, backups, etc.

    Even on my development machines with dozens of tools, containers, and multiple kernel versions, I rarely exceed 40-50 GB on /.

  7. User

    Yes I do see a need for large data on the data partition. For example local LLMs, photos, videos, movies, etc.

  8. Claude Assistant

    Perfect! Then you definitely want to maximize that /home partition for all your media and LLMs. Here's what I'd suggest for a 2TB drive:

    Recommended layout:

    /boot/efi: 512 MB (if UEFI)
    /: 60-80 GB
    /home: ~1.92 TB
    

    Why this makes sense for your use case:

    • Local LLMs: These can be massive - 7B models are ~4-13 GB, 70B models can be 40-140 GB depending on quantization
    • Media files: 4K videos, RAW photos, movie collections eat space fast
    • You want every GB possible for actual data storage

    OS partition (60-80 GB) is still plenty for:

    • Full Arch install with multiple DEs
    • Development tools, editors, browsers
    • Docker/Podman containers
    • Ollama or other LLM runners (models go in /home)
    • Package caches and system logs

    Pro tip for LLMs: Store models in your home directory (like ~/models/ or ~/.ollama/models/) rather than system directories. This keeps them on your large partition and makes them easier to manage/backup.

    With ~1.92 TB for data, you'll have room for:

    • Dozens of LLMs in various sizes
    • Thousands of RAW photos
    • Hundreds of hours of 4K video
    • Complete movie/show collections

    No point wasting 240+ GB on an OS partition that'll never use it when you have actual data storage needs!

  9. User

    When specifying 320 in gparted, is gparted expecing GiB or bytes?

  10. Claude Assistant

    In GParted, when you type just "320" in the size field, it defaults to MiB (mebibytes), not GiB or bytes.

    To specify what you want:

    • 320 MiB: Just type 320
    • 320 GiB: Type 320 GiB or 327680 (MiB)
    • 320 GB: Type 320 GB (but GParted prefers binary units)

    Quick unit reference:

    • Default (no unit) = MiB
    • GiB = Gibibytes (1024³ bytes)
    • GB = Gigabytes (1000³ bytes)
    • You can also use: B, KiB, MiB, GiB, TiB

    So if you wanted that 320 GB partition we discussed (which I still think is way too big!), you'd need to either:

    • Type 320 GiB in the field
    • Type 327680 (since 320 × 1024 = 327,680 MiB)

    For the recommended 60-80 GiB partition, you'd type:

    • 60 GiB or 61440
    • 80 GiB or 81920

    GParted also has a dropdown menu next to the size field where you can select the unit explicitly, which helps avoid confusion!

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.