Is a cluster size of 64k not good?

Discussion in 'Wii - Backup Loaders' started by MLRX, Nov 12, 2010.

  1. MLRX
    OP

    MLRX GBAtemp Fan

    Member
    378
    0
    Apr 16, 2009
    United States
    I've read many things about how you should use a cluster size of 32k when loading games off a HDD. I'm not exactly sure what a cluster size is but can having a bigger cluster size do anything?
    Any upside to having a bigger cluster size or should I just stick to 32k?
     
  2. VashTS

    VashTS Beat it, son

    Member
    3,866
    690
    Mar 14, 2009
    United States
    Upstate NY
    i would stick with 32k, thats where im at, it works with sneek if you are into that. i don't really know what purpose it serves, but i don't think it really matters that much, depends on what you are using the hdd for.

    i just stick with what works. there is no reason to change anything if everything works. im sure there is a wiki to explain what cluster size is which im probably going to look up!
     
  3. sprogurt

    sprogurt GBAtemp Fan

    Member
    375
    5
    Dec 13, 2006
    I'm pretty sure a larger cluster size results in a larger file size (some data might not completely file a 64kb cluster so you'll be losing empty space).
     
  4. Porobu

    Porobu Gbatemps Shiny Latias

    Member
    1,042
    7
    Sep 12, 2009
    Its better to use 32k because its aligned with wii wbfs cluster
     
  5. koji2009

    koji2009 GBAtemp Maniac

    Member
    1,193
    31
    Mar 13, 2009
    United States
    In general... Larger cluster size = faster drive reading at the cost of larger file sizes (not so much a problem with big files, but lots of small files with 64k could be massively more drive space used)

    For the Wii, 32k is the standard for the drives because that's the same size that Wii discs use.


    That said, 64k should work, there just isn't any reason to use the higher size as the speed difference would be negligible and there is a small chance when playing backups that it could cause a compatibility issue.