Jackrabbit performance tuning

[LukashP <lu...@poczta.onet.pl>]

Hi,
I was wondering, what can be tuned in order to increase performance of 2
operations:
- fulltext search
- committing transactions

These are the 2 situations we are observing problems while performance
testing.
Many of the search threads log lines like (suggesting that cache is heavily
used, but thats not our application cache):

[01:45:33,890] [INFO ]
[http-8080-1][Rex,demu,081460110][DocNumberCache.get()] size=136/1024,
#accesses=1001, #hits=0, #misses=1001, cacheRatio=0%
[01:46:29,328] [INFO ]
[http-8080-1][Rex,demu,081460110][LRUNodeIdCache.contains()] num=0/10240
hits=0 miss=10000
[01:46:29,329] [INFO ] [http-8080-1][Rex,demu,081460110][BundleCache.get()]
num=847 mem=8182k max=8192k avg=9893 hits=5000 miss=5000
[01:47:13,479] [INFO ] [http-8080-1][Rex,demu,081460110][BundleCache.get()]
num=1030 mem=8191k max=8192k avg=8143 hits=22321 miss=17679
[01:47:14,388] [INFO ]
[http-8080-1][Rex,demu,081460110][LRUNodeIdCache.contains()] num=0/10240
hits=0 miss=50000
[01:47:14,389] [INFO ] [http-8080-1][Rex,demu,081460110][BundleCache.get()]
num=1889 mem=5014k max=8192k avg=2718 hits=31151 miss=18849

The second problem is that if we have at least 5-10 threads that add new
documents to repo (or modify it), and they have like 5 file attachements,
size about 100k, commit operation lasts very long.

Our repository has about 10000 documents with 5 attachements, on average
150k for a single one. DB is MSSQL 2008 DB.

And actually the third problem is that, whatever I change in repository.xml
regarding performance, the changes not occur in application. For example I
changed MssqlPersistenceManager property to , but I still can read in log:
[BundleCache.get()] num=847 mem=8182k max=8192k.
So there is still default cache size at 8.
I also tried to change 		param name="cacheSize" value="20000" 
param name="resultFetchSize" value="200" 
of SearchIndex and that also does not do anything.
One would think I'm not changing the right file, but if i set the property
to non existent, I get an exception.

Please, help,
I'm getting desperate :)

Regards
-- 
View this message in context: http://n4.nabble.com/Jackrabbit-performance-tuning-tp956611p956611.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.

Re: Jackrabbit performance tuning

[Ard Schrijvers <a....@onehippo.com>]

On Thu, Dec 10, 2009 at 2:02 AM, LukashP <lu...@poczta.onet.pl> wrote:
>
> Hi,
> I was wondering, what can be tuned in order to increase performance of 2
> operations:
> - fulltext search

This just depends on how you fulltext search: also see [1]

Note that if you are concurrently searching and writing, that a search
is blocked until the indexing queue is empty

Regards Ard

[1] http://n4.nabble.com/Explanation-and-solutions-of-some-Jackrabbit-queries-regarding-performance-td516614.html#a516614

> - committing transactions
>
> These are the 2 situations we are observing problems while performance
> testing.
> Many of the search threads log lines like (suggesting that cache is heavily
> used, but thats not our application cache):
>

Re: Jackrabbit performance tuning

[Alexander Klimetschek <ak...@day.com>]

On Thu, Dec 10, 2009 at 02:02, LukashP <lu...@poczta.onet.pl> wrote:
> And actually the third problem is that, whatever I change in repository.xml
> regarding performance, the changes not occur in application.

For existing workspaces, you have to change the workspace.xml.

See also http://jackrabbit.apache.org/jackrabbit-configuration.html
(section at the top)

Regards,
Alex

-- 
Alexander Klimetschek
alexander.klimetschek@day.com