Note that there are some explanatory texts on larger screens.

plurals
  1. POFastest file access/storage?
    primarykey
    data
    text
    <p>I have about 750,000,000 files I need to store on disk. What's more is I need to be able to access these files randomly--any given file at any time--in the <b>shortest time possible</b>. What do I need to do to make accessing these files fastest?</p> <p>Think of it like a hash table, only the hash keys are the filenames and the associated values are the files' data.</p> <p>A coworker said to organize them into directories like this: if I want to store a file named "foobar.txt" and it's stored on the D: drive, put the file in "D:\f\o\o\b\a\r.\t\x\t". He couldn't explain <i>why</i> this was a good idea though. Is there anything to this idea?</p> <p>Any ideas?</p> <p><b>The crux of this is <i>finding</i> a file. What's the fastest way to find a file <i>by name</i> to open?</b></p> <p>EDIT:</p> <p><li>I have no control over the file system upon which this data is stored. It's going to be NTFS or FAT32.</li> <li>Storing the <i>file data</i> in a database is not an option.</li> <li>Files are going to be very small--maximum of probably 1 kb.</li> <li>The drives are going to be solid state.</li> <li>Data access is virtually random, but I could probably figure out a priority for each file based on how often it is requested. Some files will be accessed much more than others.</li> <li>Items will constantly be added, and sometimes deleted.</li> <li>It would be impractical to consolidate multiple files into single files because there's no logical association between files.</li> <li>I would love to gather some metrics by running tests on this stuff, but that endeavour could become as consuming as the project itself!</li></p> <p>EDIT2:</p> <p>I want to upvote several thorough answers, whether they're spot-on or not, and cannot because of my newbie status. Sorry guys!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload