Hi, Nicolas, Just a note: Having one searcher is far enough for ordinary usage, even some production sites. But I do see some throughput gain through increasing the number of searchers.
Those searchers should either be opened on an static index, or be synchronized to open/close cleanly, to avoid any exceptions. -- Chris Lu ------------------------- Instant Full-Text Search On Any Database/Application site: http://www.dbsight.net demo: http://search.dbsight.com On 2/26/07, Nicolas Lalevée <[EMAIL PROTECTED]> wrote:
Le lundi 26 février 2007 12:38, Mohammad Norouzi a écrit: > No. actually I dont close the searcher. I just set a flag to true or false. > my considerations are: > [please note I provided a ResultSet so I display the result page by page > and dont load all the result in a list] > 1- should I open a searcher for each user? and one reader for all user > session? > 2- or create a pool of searcher and one reader for all searcher? > 3- or a pool of searcher and each has its own reader. but never close them > just set a flag to true. > > which one? I probably miss something here, because I will continue answer the same : have only one instance of an index searcher in your entire web application. Nicolas >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
