[jira] [Resolved] (OAK-3986) simple performance regression IT (that would fail in case commitRoots would not be purged)
[ https://issues.apache.org/jira/browse/OAK-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved OAK-3986. -- Resolution: Fixed Fix Version/s: (was: 1.4) 1.3.16 reactivated test in http://svn.apache.org/viewvc?rev=1729806=rev and travis looks happy. Closing therefore. > simple performance regression IT (that would fail in case commitRoots would > not be purged) > -- > > Key: OAK-3986 > URL: https://issues.apache.org/jira/browse/OAK-3986 > Project: Jackrabbit Oak > Issue Type: Test > Components: jcr >Affects Versions: 1.3.15 >Reporter: Stefan Egli >Assignee: Stefan Egli >Priority: Minor > Fix For: 1.3.16 > > > There should be a performance regression IT that measures a couple of > addNode/removeNode/setProperties on a particular node to ensure performance > remains constant over time. Such a test pattern used to show a degradation > over time due to OAK-1794 but got fixed in OAK-2528 long time ago. This is > just to have a proper IT. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OAK-3986) simple performance regression IT (that would fail in case commitRoots would not be purged)
[ https://issues.apache.org/jira/browse/OAK-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved OAK-3986. -- Resolution: Fixed test modified in rev 1729174 as follows: * margin was erroneously at 20% - adjusted that to the intended 50% (we can go higher if this still doesn't turn out enough for travis) * ignoring first failing iteration (which effectively would allow one performance-slowdown-spike) * increased number of loops from 10 to 15 to ensure the above relaxed test parameters dont unintentionally result in missing a failing test run > simple performance regression IT (that would fail in case commitRoots would > not be purged) > -- > > Key: OAK-3986 > URL: https://issues.apache.org/jira/browse/OAK-3986 > Project: Jackrabbit Oak > Issue Type: Test > Components: jcr >Affects Versions: 1.3.15 >Reporter: Stefan Egli >Assignee: Stefan Egli >Priority: Minor > Fix For: 1.3.16 > > > There should be a performance regression IT that measures a couple of > addNode/removeNode/setProperties on a particular node to ensure performance > remains constant over time. Such a test pattern used to show a degradation > over time due to OAK-1794 but got fixed in OAK-2528 long time ago. This is > just to have a proper IT. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OAK-3986) simple performance regression IT (that would fail in case commitRoots would not be purged)
[ https://issues.apache.org/jira/browse/OAK-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved OAK-3986. -- Resolution: Fixed > simple performance regression IT (that would fail in case commitRoots would > not be purged) > -- > > Key: OAK-3986 > URL: https://issues.apache.org/jira/browse/OAK-3986 > Project: Jackrabbit Oak > Issue Type: Test > Components: jcr >Affects Versions: 1.3.15 >Reporter: Stefan Egli >Assignee: Stefan Egli >Priority: Minor > Fix For: 1.3.16 > > > There should be a performance regression IT that measures a couple of > addNode/removeNode/setProperties on a particular node to ensure performance > remains constant over time. Such a test pattern used to show a degradation > over time due to OAK-1794 but got fixed in OAK-2528 long time ago. This is > just to have a proper IT. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
