Anywho. Neoventi will most likely not have code for building the index. Instead, _if you want it_, you can specify that your index drive is stored on a ramdisk and modify your bootrc to build the index on startup.
neoventi won't care whether your index is on a ramdisk or a regular one. If you want to rebuild it on each boot, that's fine. That should already work, really, using venti/buildindex. That said, I _will_ be looking at redesigning the index. Fairly sure from previous estimates that i can get at least 2x as many entries per sector. Probably more. The structure needs some serious work, venti's high-level design is good IMO, but the details are atrocious. I also intend to make rebuilding the index, using neoventi/buildindex, significantly faster than it is at present, so that won't be an entirely unreasonable option. But, consider the alternative: a 25TiB venti would require something like 250GiB of RAM. 25TiB of HDD space is much, much, much more practical than 250GiB of RAM, even today, even _before_ the recent RAM spikes. 250GiB of SSD space, _even if you assume_ it will wear out quickly, is still more practical. Rebuilding the index once every other year would be much more practical than _requiring_ massive RAM usage. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T4d8ba4236feb5d92-Maf3fd5d8fe8f5636744cd684 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
