[jira] [Commented] (SLING-3290) Long startup time with many vanityPath or alias
[ https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13874746#comment-13874746 ] Antonio Sanso commented on SLING-3290: -- [~justinedelson] adding profile information {code} org.apache.sling.performance.tests.StartupWithManyVanityPath.runTest(),18272 org.apache.sling.performance.PerformanceTest$Helper.init(String, Session, SlingRepository),18272 org.apache.sling.resourceresolver.impl.mapping.MapEntries.init(MapConfigurationProvider, BundleContext, EventAdmin),18272 org.apache.sling.resourceresolver.impl.mapping.MapEntries.doInit(),18272 org.apache.sling.resourceresolver.impl.mapping.MapEntries.loadVanityPaths(ResourceResolver, Map),18252 org.apache.sling.resourceresolver.impl.helper.ResourceIteratorDecorator.next(),15500 {code} as expected the looping through the search results is the bottleneck Long startup time with many vanityPath or alias --- Key: SLING-3290 URL: https://issues.apache.org/jira/browse/SLING-3290 Project: Sling Issue Type: Improvement Reporter: Antonio Sanso Assignee: Antonio Sanso Labels: vanity Attachments: StartupWithManyVanityPath.jpg When many vanityPath or alias are present the system take long time to startup , Same when a vanityPath/alias is removed or updated . The reason behind is the usage of a query that updates the global mapentry. I have added a new Test to the performance test suite and this is the outcome {code} 0 vanityPath 16ms 1 vanityPath 19ms 10 vanityPath 70ms 100 vanityPath111ms 1000 vanityPath 200ms 1 vanityPath 1173ms 3 vanityPath 3358ms {code} -- This message was sent by Atlassian JIRA (v6.1.5#6160)
Re: Long startup time with many vanityPath or alias
anyone :) ? On Dec 19, 2013, at 10:02 AM, Antonio Sanso asa...@adobe.com wrote: hi *, in SLING-3290 [0] I have started to write some performance test regarding long startup time with many vanityPath or alias. As you might see from the attached graph the startup time increases considerably with the number of vanityPath. The same should applies to aliases (I am writing the test case). The reason behind this is comment and should be IMHO the usage of a query that updates the global map entry. In fact the issue doesn't occur only at startup but as well every time a vanityPath/alias is updated. IMHO would be nice to try to improve this situation. WDYT? regards antonio [0] https://issues.apache.org/jira/browse/SLING-3290
Re: Long startup time with many vanityPath or alias
On Mon, Jan 6, 2014 at 2:03 PM, Antonio Sanso asa...@adobe.com wrote: anyone :) ?... I see only observations in https://issues.apache.org/jira/browse/SLING-3290, what are you looking for? If it's agreement that long startup times are bad, I do agree ;-) -Bertrand
Re: Long startup time with many vanityPath or alias
On Jan 6, 2014, at 2:10 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Mon, Jan 6, 2014 at 2:03 PM, Antonio Sanso asa...@adobe.com wrote: anyone :) ?... I see only observations in https://issues.apache.org/jira/browse/SLING-3290, what are you looking for? right :) It would be nice to try to come with an approach to improve the situation, This issue would affect not only the startup time but the update as well . Also the alias features is impacted. IMHO we should replace the search for vanityPath/aliases and come up with a new solution. This is the only way to scale regards antonio If it's agreement that long startup times are bad, I do agree ;-) -Bertrand
Re: Long startup time with many vanityPath or alias
Hi, On Mon, Jan 6, 2014 at 8:18 AM, Antonio Sanso asa...@adobe.com wrote: On Jan 6, 2014, at 2:10 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Mon, Jan 6, 2014 at 2:03 PM, Antonio Sanso asa...@adobe.com wrote: anyone :) ?... I see only observations in https://issues.apache.org/jira/browse/SLING-3290, what are you looking for? right :) It would be nice to try to come with an approach to improve the situation, This issue would affect not only the startup time but the update as well . Also the alias features is impacted. IMHO we should replace the search for vanityPath/aliases and come up with a new solution. This is the only way to scale Have you done any profiling to see where the time is going? My personal opinion is that supporting 10k vanity paths is a non-goal, but that's just me :) I believe Felix has proposed a solution to migrate vanity paths from wherever they are defined into /etc/map through some kind of approval workflow. Search the list archives for more details. Justin regards antonio If it's agreement that long startup times are bad, I do agree ;-) -Bertrand
Re: Long startup time with many vanityPath or alias
On Mon, Jan 6, 2014 at 3:00 PM, Justin Edelson jus...@justinedelson.com wrote: ...My personal opinion is that supporting 10k vanity paths is a non-goal, but that's just me :)... I would agree but users are creative sometimes ;-) Worst case, we might provide a way to disable the default vanity paths handling completely and let people implement their own variant, for exotic use cases. ...I believe Felix has proposed a solution to migrate vanity paths from wherever they are defined into /etc/map through some kind of approval workflow. Search the list archives for more details I remember these discussions but haven't followed in detail. Looking at this I tried to list all the ways that we have to map incoming URLs to resources and vice-versa, and it makes me wonder if we really need all these mechanisms: a) Vanity URLs, sling:vanityPath http://sling.apache.org/old-stuff/request-processing.html b) Mappings via /etc/map with sling:match, sling:alias, sling:internalRedirect, sling:redirect http://sling.apache.org/documentation/the-sling-engine/mappings-for-resource-resolution.html c) sling:alias and sling:redirect on any resource Documented a the same URL as b) d) Resource resolver virtual URLs No docs? e) Resource resolver URL mappings No docs? f) Resource resolver namespace mangling No docs? Not sure if this list is even complete... -Bertrand
Long startup time with many vanityPath or alias
hi *, in SLING-3290 [0] I have started to write some performance test regarding long startup time with many vanityPath or alias. As you might see from the attached graph the startup time increases considerably with the number of vanityPath. The same should applies to aliases (I am writing the test case). The reason behind this is comment and should be IMHO the usage of a query that updates the global map entry. In fact the issue doesn't occur only at startup but as well every time a vanityPath/alias is updated. IMHO would be nice to try to improve this situation. WDYT? regards antonio [0] https://issues.apache.org/jira/browse/SLING-3290
[jira] [Updated] (SLING-3290) Long startup time with many vanityPath or alias
[ https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Sanso updated SLING-3290: - Attachment: StartupWithManyVanityPath.jpg attaching report for StartupWithManyVanityPath that shows how the startup time increases with the vanitypaths Long startup time with many vanityPath or alias --- Key: SLING-3290 URL: https://issues.apache.org/jira/browse/SLING-3290 Project: Sling Issue Type: Improvement Reporter: Antonio Sanso Assignee: Antonio Sanso Attachments: StartupWithManyVanityPath.jpg When many vanityPath or alias are present the system take long time to startup , Same when a vanityPath/alias is removed or updated . The reason behind is the usage of a query that updates the global mapentry. I have added a new Test to the performance test suite and this is the outcome {code} 0 vanityPath 16ms 1 vanityPath 19ms 10 vanityPath 70ms 100 vanityPath111ms 1000 vanityPath 200ms 1 vanityPath 1173ms 3 vanityPath 3358ms {code} -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Created] (SLING-3290) Long startup time with many vanityPath or alias
Antonio Sanso created SLING-3290: Summary: Long startup time with many vanityPath or alias Key: SLING-3290 URL: https://issues.apache.org/jira/browse/SLING-3290 Project: Sling Issue Type: Improvement Reporter: Antonio Sanso When many vanityPath or alias are present the system take long time to startup , Same when a vanityPath/alias is removed or updated . The reason behind is the usage of a query that updates the global mapentry. I have added a new Test to the performance test suite and this is the outcome {code} 0 vanityPath16ms 1 vanityPath 19ms 10 vanityPath 70ms 100 vanityPath 111ms 1000 vanityPath 200ms 1 vanityPath1173ms 3 vanityPath3358ms {code} -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (SLING-3290) Long startup time with many vanityPath or alias
[ https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Sanso updated SLING-3290: - Description: When many vanityPath or alias are present the system take long time to startup , Same when a vanityPath/alias is removed or updated . The reason behind is the usage of a query that updates the global mapentry. I have added a new Test to the performance test suite and this is the outcome {quote} 0 vanityPath16ms 1 vanityPath 19ms 10 vanityPath 70ms 100 vanityPath 111ms 1000 vanityPath 200ms 1 vanityPath1173ms 3 vanityPath3358ms {quote} was: When many vanityPath or alias are present the system take long time to startup , Same when a vanityPath/alias is removed or updated . The reason behind is the usage of a query that updates the global mapentry. I have added a new Test to the performance test suite and this is the outcome {code} 0 vanityPath16ms 1 vanityPath 19ms 10 vanityPath 70ms 100 vanityPath 111ms 1000 vanityPath 200ms 1 vanityPath1173ms 3 vanityPath3358ms {code} Long startup time with many vanityPath or alias --- Key: SLING-3290 URL: https://issues.apache.org/jira/browse/SLING-3290 Project: Sling Issue Type: Improvement Reporter: Antonio Sanso When many vanityPath or alias are present the system take long time to startup , Same when a vanityPath/alias is removed or updated . The reason behind is the usage of a query that updates the global mapentry. I have added a new Test to the performance test suite and this is the outcome {quote} 0 vanityPath 16ms 1 vanityPath 19ms 10 vanityPath 70ms 100 vanityPath111ms 1000 vanityPath 200ms 1 vanityPath 1173ms 3 vanityPath 3358ms {quote} -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Assigned] (SLING-3290) Long startup time with many vanityPath or alias
[ https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Sanso reassigned SLING-3290: Assignee: Antonio Sanso Long startup time with many vanityPath or alias --- Key: SLING-3290 URL: https://issues.apache.org/jira/browse/SLING-3290 Project: Sling Issue Type: Improvement Reporter: Antonio Sanso Assignee: Antonio Sanso When many vanityPath or alias are present the system take long time to startup , Same when a vanityPath/alias is removed or updated . The reason behind is the usage of a query that updates the global mapentry. I have added a new Test to the performance test suite and this is the outcome {quote} 0 vanityPath 16ms 1 vanityPath 19ms 10 vanityPath 70ms 100 vanityPath111ms 1000 vanityPath 200ms 1 vanityPath 1173ms 3 vanityPath 3358ms {quote} -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (SLING-3290) Long startup time with many vanityPath or alias
[ https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13849240#comment-13849240 ] Antonio Sanso commented on SLING-3290: -- {code} 0 vanityPath 16ms 1 vanityPath 19ms 10 vanityPath 70ms 100 vanityPath 111ms 1000 vanityPath 200ms 1 vanityPath 1173ms 3 vanityPath 3358ms {code} Long startup time with many vanityPath or alias --- Key: SLING-3290 URL: https://issues.apache.org/jira/browse/SLING-3290 Project: Sling Issue Type: Improvement Reporter: Antonio Sanso Assignee: Antonio Sanso When many vanityPath or alias are present the system take long time to startup , Same when a vanityPath/alias is removed or updated . The reason behind is the usage of a query that updates the global mapentry. I have added a new Test to the performance test suite and this is the outcome {code} 0 vanityPath 16ms 1 vanityPath 19ms 10 vanityPath 70ms 100 vanityPath111ms 1000 vanityPath 200ms 1 vanityPath 1173ms 3 vanityPath 3358ms {code} -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (SLING-3290) Long startup time with many vanityPath or alias
[ https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Sanso updated SLING-3290: - Description: When many vanityPath or alias are present the system take long time to startup , Same when a vanityPath/alias is removed or updated . The reason behind is the usage of a query that updates the global mapentry. I have added a new Test to the performance test suite and this is the outcome {code} 0 vanityPath16ms 1 vanityPath 19ms 10 vanityPath 70ms 100 vanityPath 111ms 1000 vanityPath 200ms 1 vanityPath1173ms 3 vanityPath3358ms {code} was: When many vanityPath or alias are present the system take long time to startup , Same when a vanityPath/alias is removed or updated . The reason behind is the usage of a query that updates the global mapentry. I have added a new Test to the performance test suite and this is the outcome {quote} 0 vanityPath16ms 1 vanityPath 19ms 10 vanityPath 70ms 100 vanityPath 111ms 1000 vanityPath 200ms 1 vanityPath1173ms 3 vanityPath3358ms {quote} Long startup time with many vanityPath or alias --- Key: SLING-3290 URL: https://issues.apache.org/jira/browse/SLING-3290 Project: Sling Issue Type: Improvement Reporter: Antonio Sanso Assignee: Antonio Sanso When many vanityPath or alias are present the system take long time to startup , Same when a vanityPath/alias is removed or updated . The reason behind is the usage of a query that updates the global mapentry. I have added a new Test to the performance test suite and this is the outcome {code} 0 vanityPath 16ms 1 vanityPath 19ms 10 vanityPath 70ms 100 vanityPath111ms 1000 vanityPath 200ms 1 vanityPath 1173ms 3 vanityPath 3358ms {code} -- This message was sent by Atlassian JIRA (v6.1.4#6159)