jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-3026) davex remoting has a performance bottleneck due limit of 2 http connections
Date Tue, 26 Jul 2011 14:25:10 GMT

    [ https://issues.apache.org/jira/browse/JCR-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071119#comment-13071119
] 

angela commented on JCR-3026:
-----------------------------

applied patch with quite some modification. specially the comments did not match the code
which made it a bit cumbersome.
in addition it would be nice if the formatting would match the overall coding style used in
jackrabbit.

thanks anyway for your effort.


> davex remoting has  a performance bottleneck due limit of 2 http connections
> ----------------------------------------------------------------------------
>
>                 Key: JCR-3026
>                 URL: https://issues.apache.org/jira/browse/JCR-3026
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-spi2dav
>    Affects Versions: 2.2.5
>            Reporter: chad davis
>            Assignee: angela
>              Labels: dav, davex, performance, remoting
>             Fix For: 2.3.0
>
>         Attachments: JCR-3026_Spi2davRepositoryServiceFactory.java.patch, JCR-3026_Spi2davexRepositoryServiceFactory.java.patch,
JCR-3026_org.apache.jackrabbit.spi2dav.RepositoryServiceImpl.java.patch, JCR-3026_org.apache.jackrabbit.spi2davex.RepositoryServiceImpl.java.patch
>
>
> The spi2dav service implementation use of HttpClient did not support configuration of
the maximum amount of http connections to the server.  The default value, in the HttpClient
code, is two. This was a performance bottleneck.  This work makes the number of connections
configurable via a parameter to the map passed to the repository factory.  
> It also fixes a concurrency issue which was exposed by the increased concurrency effected
by this work.  This fix is a replacement of a HashMap cache of client connections with a ConcurrentHashMap,
thanks to the java 1.5 available in Jackrabbit 2.x
> USAGE: 
> Set the number of connections (Spi2davRepositoryServiceFactory.PARAM_MAX_HTTP_CONNECTIONS)
when creating a factory via the dav or davex rep factories.  Default is 20.
> NOTE: 
> See also the server side fixes: JCR-3027  The patch on that ticket allows configuration
of the concurrency level on the server, which should be tuned in conjunction with the client
side connection levels.  
>  

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message