Hi Stefan, you might want to consider org.apache.lucene.store.FileSwitchDirectory before going for the symlinks approach. Sorry I don't know the effect nor recommended file types, I would naively start setting the smallest on SSD, then perform tests, but that's possibly not the best scenario: under stress the most-frequently used files will likely be cached by your operating system, so to achieve the perfect setup you would need to find which is the most frequently used types of files, excluding what fits in your os cache.. I assume it's going to change with configurations, index sizes and use cases: not an easy task.
Sanne 2010/8/26 Stefan Nikolic <stefan.niko...@gmail.com>: > Hi everyone, > > I'm trying to figure out the effects on search performance of using the > non-CFS format and spreading the various underlying files to different > disks/media types. For example, I'm considering moving a segment's various > .t* term-related files onto a solid-state drive, the .fdx/.fdt > stored-fields-related files onto a standard rotational drive, and using > symlinks to hide all of this from Lucene. > > Any ideas on what the performance effects of such a setup would be? Which > files would you recommend putting on the slower media, and which on the > faster media? > > Thanks! > > -Stefan > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
