jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From avim <avi.mor...@timetoknow.org>
Subject Re: Profiling shows Session management to be a hotspot - session pooling etc
Date Tue, 27 Mar 2007 11:14:51 GMT



Shaun Barriball wrote:
> 
> Hi all,
> We're currently CPU profiling an application which uses the SessionInView
> pattern to create a new JCR session (with JackRabbit) for each request.
> 
> Profiling shows that around:
>  - 11.4% of the CPU time is in releaseSession(). In particular around 5%
> of
> this is in ItemManager.evictItem().
>  - 0.08% of the CPU time is in getSession()
> 
> For each request the application is just reading a set of nodes (upto
> around
> 100) to generate a web page. We're using JackRabbit 1.2.1 with Oracle.
> 
> Any recommendations for how to resolve this overhead?
>  - should we consider pooling sessions?
>  - any way to optimise the session usage given the nodes are all
> read-only?
> If you have no write operations, you can use a single session for the hole
> application(!?)
> All help appreciated.
> Regards,
> Shaun.
> 
> 
> 		
> ___________________________________________________________ 
> All New Yahoo! Mail – Tired of Vi@gr@! come-ons? Let our SpamGuard protect
> you. http://uk.docs.yahoo.com/nowyoucan.html
> 
> 

-- 
View this message in context: http://www.nabble.com/Profiling-shows-Session-management-to-be-a-hotspot---session-pooling-etc-tf3472134.html#a9690383
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.


Mime
View raw message