I cannot say anything about performance... but having a "magnolia- module-nutch" would be nice anyway! With a good part of the content now being stored in the dms or data repository, searches over the website repository will not deliver very good results anyway. Also when you reuse content in websites in other places (say, you have a collection of news pages and their abstracts are being displayed in an automatically generated news overview, a search on the website repository will not return the news overview page as search result. Nutch on the other hand will index the _output_ (instead of the repository) and will therefore return the correct search results.

The downside to it: It's not so easy to adapte the search results to the users permissions...

will

On 05.08.2008, at 04:25, Miranda Jones wrote:

I don't know if it's normal, per se, but we experienced the same thing
with far far fewer pages than 5000.  Maybe on the order of 75-100
pages.  Most searches were fine, but certain words that would be
common search terms on our site would for some reason totally kill it.
CPU usage and load on the machine would go through the roof and all
the web applications would stop responding.  We ended up switching to
indexing the site with Nutch and implementing the search in a separate
webapp.


On Mon, Aug 4, 2008 at 8:54 PM, Ruben Reusser <user- [EMAIL PROTECTED]> wrote:

I am experiencing some problem with searches on a larger site. Say for example you have 5000+ pages in magnolia all created by superuser and you search for super - the search takes an awful long time. Am I doing something wrong or is this normal behavior?

--
Miranda Jones
Objective Consulting, Inc.
http://www.spiders.com

----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------


----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------

Reply via email to