jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexander Klimetschek <aklim...@day.com>
Subject Re: Performance of Jackrabbit
Date Thu, 23 Jul 2009 11:00:05 GMT
On Thu, Jul 23, 2009 at 9:31 AM, Ajai<ajaiking@gmail.com> wrote:
> http://www.nabble.com/file/p24620741/ThreadFeeder.java ThreadFeeder.java
> http://www.nabble.com/file/p24620741/repository.xml repository.xml
> http://www.nabble.com/file/p24620741/indexingconfiguration.xml
> indexingconfiguration.xml
>
> Kindly let me know your suggestions.

>From a quick look at your code it looks like you create a flat
hierarchy with all nodes on the same level. You should try to
distribute the load by creating more subfolders (which should follow
some useful structure, eg. dates like 2009/07/23 works with most
content). The limit where Jackrabbit gets a bit slower is at around
10k child nodes.

Apart from that I could imagine the text extraction of the search
index slows down things a bit (although they should happen in the
background if they take too long) if you throw a lot of documents at
them at once. Disabling the search index could give a measurement of
that effect.

Finally, as already mentioned, an embedded database such as derby and
the appropriate pm are always faster than remote dbs. The use of the
file datastore is already good.

Regards,
Alex

-- 
Alexander Klimetschek
alexander.klimetschek@day.com

Mime
View raw message