01-23-2015, 03:10 AM
great, thanks for the tip.
that makes perfect sense and is working well so far, but ive run into my first problem.
5letters.txt is contains ~6900 words, and is ~40 kb, 2words.txt contains ~47,000,000 words and is ~500mb. threewords.txt got to AOUADDOGEYOFTEN and was 200gb when i cancelled it, as there wasnt ample space to let it finish.
i have a couple of thoughts; it could be that there is come kind of inter-os problem that is making third.txt inflate in size (combinator is running in vm and outputting to osx) but i dont really think this is the case. it could be that i could manage this size escalation by splitting 5letters into smaller sections, but either way it neccessitates storage on a an external, which is going to be usb2. this would slow things down, yeah? and given that storage is my limiting factor, id have to generate sections, test them against the password, and delete them before generating the next section.
let me know what you think.
that makes perfect sense and is working well so far, but ive run into my first problem.
5letters.txt is contains ~6900 words, and is ~40 kb, 2words.txt contains ~47,000,000 words and is ~500mb. threewords.txt got to AOUADDOGEYOFTEN and was 200gb when i cancelled it, as there wasnt ample space to let it finish.
i have a couple of thoughts; it could be that there is come kind of inter-os problem that is making third.txt inflate in size (combinator is running in vm and outputting to osx) but i dont really think this is the case. it could be that i could manage this size escalation by splitting 5letters into smaller sections, but either way it neccessitates storage on a an external, which is going to be usb2. this would slow things down, yeah? and given that storage is my limiting factor, id have to generate sections, test them against the password, and delete them before generating the next section.
let me know what you think.