[ http://jira.codehaus.org/browse/MRM-142?page=comments#action_71445 ] Brett Porter commented on MRM-142: ----------------------------------
did some performance analysis while I was there. It appears that indexing the JAR files is not the time consuming operation, but rather the indexing, checksumming and reading the POMs: discovery: 7% (mostly the directory scanner - a total of 6%) indexing records: 53% reading records: 32% Breaking down the last one: reading pom: 16% reading checksum: 14% Breaking down reading the POM: resolving: 3% (these are all local) building: 13% Breaking down building: interpolation: 5% This was with no existing index. It may be more skewed towards indexing if it has to delete all the records as it goes. > possible memory leak > -------------------- > > Key: MRM-142 > URL: http://jira.codehaus.org/browse/MRM-142 > Project: Maven Repository Manager > Issue Type: Bug > Components: indexing > Reporter: Brett Porter > Assigned To: Brett Porter > Fix For: 1.0-beta-1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > need to investigate if there is a memory leak, since the server received an > OOME some time after successfully completing a full index with 1Gb heap with > just some browsing/searching. It is most likely in the indexing itself, but > there may be some in the browse/search interface too -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
