AnsweredAssumed Answered

Querying is not scalable? (cross-posted from JCR forum)

Question asked by panokhin on May 16, 2006
Latest reply on May 17, 2006 by kevinr
This is cross-posted from JCR forum as I feel I may have problems with the test setup. If you see any, I'd very much wanted to hear your comments.

I'm currently evaluating Alfresco for use as a platform for our electronic tendering service. We really like the architecture and code quality, however there are some concerns about its scalability.

I'm trying to do a simple test of loading about 1700 objects (I'll include the complete model and sample code below) and querying them using JCR API (we decided to go with JCR since it seems to becoming a widely adopted standard).

The model is like this: Site->Buyer->Buyer->Notice->LangProperty
There are about 1300 of LangProperties, 300 of Notices and 100 of Buyers.
The computer is AMD Athlon 64 3200+ with 2Gb memory, running both Oracle XE and JBoss+Alfresco.
I ran this XPath query:
Query q = qm.createQuery("//dg:notices/dg:langProperties[jcr:contains(@dg:propText,'solicitation')]/..",Query.XPATH);
and results were quite disappointing - between 60 and 80 seconds on different runs.

So, I wanted to ask 3 questions:
1. Is this poor result due to the fact that JCR support is new in Alfresco, so it's going to be changed in near future to be more scalable?
2. If we use Alfresco search API instead, will it scale better or the problem is in the model we use: few nodes but many (large text) properties?
3. Are there any support (current or planned) in Alfresco's version of JCR search or it's own Lucene search for language-specific search modifiers (e.g. stemming, base letter conversion, fuzzy search)?

Thank you,
Looking forward to hearing your advice,