Hi! We are working in a heavy content site, with about 87,000 content objects with full-text indexing (TextIndexNg). Usually read-only, rarely writing or updating contents on the ZODB. Due to usability reasons, we'll never give "search in the whole site" search results, but "We found x results in the A section, we found y results in the B section...", although the users are able to search in the whole site. So, we are deciding about giving search results with: - One ZCatalog at the top. Launch it N times in order to give results from each path. or - N ZCatalogs, each one in one section. For managing, it's clear that the second option is more useful. (I'm trying to index the whole site at once... what a pain!!) What about the performance with high load? what is more expensive? calling 8 times the same big ZCatalog, or calling 8 different (but smaller) ZCatalogs in the same request? Thanks in advance _______________________________________ Garikoitz Araolaza Code&Syntax garaolaza@codesyntax.com Azitaingo Industrialdea P3 K E-20600-EIBAR Tel: +34 943 82 06 06
--On Montag, 2. Juni 2003 11:54 Uhr +0200 Garikoitz Araolaza <garaolaza@codesyntax.com> wrote:
Hi!
We are working in a heavy content site, with about 87,000 content objects with full-text indexing (TextIndexNg). Usually read-only, rarely writing or updating contents on the ZODB.
That's not much!
Due to usability reasons, we'll never give "search in the whole site" search results, but "We found x results in the A section, we found y results in the B section...", although the users are able to search in the whole site.
What's the problem with using one Catalog? You could limit the search by adding further constraints to the query.
So, we are deciding about giving search results with:
- One ZCatalog at the top. Launch it N times in order to give results from each path.
or
- N ZCatalogs, each one in one section.
For managing, it's clear that the second option is more useful. (I'm trying to index the whole site at once... what a pain!!)
What about the performance with high load? what is more expensive? calling 8 times the same big ZCatalog, or calling 8 different (but smaller) ZCatalogs in the same request?
*one* large ZCatalog should be choice for your site. -aj
We tried that once and found that maintaining multiple catalogs can become a *real* pain rather quickly. I recommend to go for a single catalog. HTH, Stefan --On Montag, 02. Juni 2003 11:54 +0200 Garikoitz Araolaza <garaolaza@codesyntax.com> wrote:
So, we are deciding about giving search results with:
- One ZCatalog at the top. Launch it N times in order to give results from each path.
or
- N ZCatalogs, each one in one section.
-- The time has come to start talking about whether the emperor is as well dressed as we are supposed to think he is. /Pete McBreen/
participants (3)
-
Andreas Jung -
Garikoitz Araolaza -
Stefan H. Holek