cancel
Showing results for 
Search instead for 
Did you mean: 

Advanced search SLOW!

lmoulin
Champ in-the-making
Champ in-the-making
Hello,
I have a large number of documents in the Alfresco repository (~100 000 documents).
The advanced search takes lots of time to return the results (~more than 60 seconds)
I use only the custom criteria to perform the advanced search.
I don’t use the google like search and the full text search.

I have set the following value in web-client-config.xml:
<search-max-results>100</search-max-results>

Have you got a hack to increase the performances of the advanced search?
Thanks a lot.
Luc
15 REPLIES 15

lmoulin
Champ in-the-making
Champ in-the-making
Theoretically,
The query '+@\{my.new.model\}erd_commercialisateur:"GAZ ELECTRICITE DE GRENOBLE" AND (( TYPE:"{my.new.model}custom_root_type" OR TYPE:"{http://www.alfresco.org/model/content/1.0}folder" )) ' returns 100 000 documents.

But, when I execute a query which returns only 10 documents, it is very faster (~10 seconds).

Why this big variation?

Thanks a lot
Luc

lmoulin
Champ in-the-making
Champ in-the-making
My database has the following properties:
CREATE DATABASE "ERD1.0"
  WITH OWNER = erd
       ENCODING = 'LATIN1'
       TABLESPACE = pg_default;

andy
Champ on-the-rise
Champ on-the-rise
Hi

As Derek says, Postgress was not supported or tested on V1.4 community. Issues with its use - mainly performance have been fixed in the enterprise code. You can get these fixes by paying for support or you will have to wait until the fixes are in a later community release.

None of the other issues have anything to do with your performance problem.

Regards

Andy

lmoulin
Champ in-the-making
Champ in-the-making
I have installed my application on Oracle and the advanced search runs well.
Thanks a lot.

lmoulin
Champ in-the-making
Champ in-the-making
Has this PostGre bug been fixed in the latest version?

Thanks a lot,
Luc

kevinr
Star Contributor
Star Contributor
I believe this was an Enterprise fix and made it into 2.0E and 1.4.2E (i think) the fix should be in HEAD now so will be in the 2.1 Community release.

Thanks,

Kevin