[
https://issues.apache.org/jira/browse/SVN-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Foad updated SVN-4669:
-----------------------------
Description:
When there is explicit mergeinfo on thousands of subtrees, a merge at the
subtree root can take several hours.
The merge code makes multiple (4 in my test) synchronous
svn_ra_get_location_segments() queries to the server for each subtree with
mergeinfo. If, for example, 3600 subtrees have mergeinfo and each query takes
0.25 second, that adds up to an hour.
This is related to but different from the memory usage issue SVN-4667. The
results of most of these queries are stored temporarily and account for only
10% of the total memory used in my test.
Possible approaches to improving the merge code are: (1) make the queries much
more efficient; and (2) analyse how the results are used and eliminate
unnecessary queries.
The work-flow approach to improving the experience is: get the number of
subtrees with mergeinfo down to none or very few.
(WANdisco's internal issue id: SVNB-1952.)
was:
When there is explicit mergeinfo on thousands of subtrees, a merge at the
subtree root can take several hours.
The merge code makes multiple (4 in my test) synchronous
svn_ra_get_location_segments() queries to the server for each subtree with
mergeinfo. If, for example, 3600 subtrees have mergeinfo and each query takes
0.25 second, that adds up to an hour.
This is related to but different from the memory usage issue SVN-4667. The
results of most of these queries are stored temporarily and account for only
10% of the total memory used in my test.
Possible approaches to improving the merge code are: (1) make the queries much
more efficient; and (2) analyse how the results are used and eliminate
unnecessary queries.
The work-flow approach to improving the experience is: get the number of
subtrees with mergeinfo down to none or very few.
> Merge with much subtree mergeinfo takes hours
> ---------------------------------------------
>
> Key: SVN-4669
> URL: https://issues.apache.org/jira/browse/SVN-4669
> Project: Subversion
> Issue Type: Bug
> Affects Versions: 1.9.5
> Reporter: Julian Foad
> Labels: performance
>
> When there is explicit mergeinfo on thousands of subtrees, a merge at the
> subtree root can take several hours.
> The merge code makes multiple (4 in my test) synchronous
> svn_ra_get_location_segments() queries to the server for each subtree with
> mergeinfo. If, for example, 3600 subtrees have mergeinfo and each query takes
> 0.25 second, that adds up to an hour.
> This is related to but different from the memory usage issue SVN-4667. The
> results of most of these queries are stored temporarily and account for only
> 10% of the total memory used in my test.
> Possible approaches to improving the merge code are: (1) make the queries
> much more efficient; and (2) analyse how the results are used and eliminate
> unnecessary queries.
> The work-flow approach to improving the experience is: get the number of
> subtrees with mergeinfo down to none or very few.
> (WANdisco's internal issue id: SVNB-1952.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
