Forum: Ferret Best Practices for Searching Multiple Indexes -- multi reade

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
6d93bda89be85bc834adeab757a1742b?d=identicon&s=25 Erik Morton (Guest)
on 2007-04-01 16:59
(Received via mailing list)
Back in September (http://rubyforge.org/pipermail/ferret-talk/2006-
September/001210.html) Dave said:

"Another use-case might be to have multiple indexes to speed up
indexing. If for example you are scraping websites it is a very good
idea to have multiple scraping processes. The best way to do this is
to have each process indexing to its own index. You could then search
all indexes at once using a MultiReader or you could also merge all
indexes into a single index."

Does anyone have any recommendations as to whether one method is
superior to the other? We have a system where we build multiple
indexes from scraping websites and need to expose the indexes as a
web application--the web app will only search the index and will
never modify it. If we have 30 or 40 indexes, would it be better to
combine them or use a MultiReader? How would we combine them? Thanks
in advance.

Erik
This topic is locked and can not be replied to.