[jira] [Commented] (SLING-3290) Long startup time with many vanityPath
[
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14255794#comment-14255794
]
Antonio Sanso commented on SLING-3290:
--
{code}
10 vanityPath 16ms
100 vanityPath 17ms
1000 vanityPath 19ms
1 vanityPath 30ms
{code}
using the improvement made in SLING-4216 and setting maxCachedVanityPathEntries
to 0 we obtain the data above.
Long startup time with many vanityPath
--
Key: SLING-3290
URL: https://issues.apache.org/jira/browse/SLING-3290
Project: Sling
Issue Type: Improvement
Components: ResourceResolver
Reporter: Antonio Sanso
Assignee: Antonio Sanso
Labels: vanity
Attachments: BloomFilterUtilsTest.txt, SLING-3290-patch-nobloom.txt,
SLING-3290-patch.txt, 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.3.4#6332)
[jira] [Commented] (SLING-3290) Long startup time with many vanityPath
[
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14237716#comment-14237716
]
Antonio Sanso commented on SLING-3290:
--
just for the record. Solving SLING-4216 probably would also have as nice side
effect to solve the long startup issue described here.
Long startup time with many vanityPath
--
Key: SLING-3290
URL: https://issues.apache.org/jira/browse/SLING-3290
Project: Sling
Issue Type: Improvement
Components: ResourceResolver
Reporter: Antonio Sanso
Assignee: Antonio Sanso
Labels: vanity
Attachments: BloomFilterUtilsTest.txt, SLING-3290-patch-nobloom.txt,
SLING-3290-patch.txt, 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.3.4#6332)
[jira] [Commented] (SLING-3290) Long startup time with many vanityPath
[
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14112108#comment-14112108
]
Carsten Ziegeler commented on SLING-3290:
-
Patch lgtm
Long startup time with many vanityPath
--
Key: SLING-3290
URL: https://issues.apache.org/jira/browse/SLING-3290
Project: Sling
Issue Type: Improvement
Components: ResourceResolver
Reporter: Antonio Sanso
Assignee: Antonio Sanso
Labels: vanity
Attachments: BloomFilterUtilsTest.txt, SLING-3290-patch-nobloom.txt,
SLING-3290-patch.txt, 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.2#6252)
[jira] [Commented] (SLING-3290) Long startup time with many vanityPath
[
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14085847#comment-14085847
]
Carsten Ziegeler commented on SLING-3290:
-
I'm note sure if we should mix the two issues for now. As Felix points out, the
long term goal is to just use /etc/map as the source of truth (some time ago I
created SLING-3206 for a first step). Startup might still be slow if we have to
traverse a large tree in /etc/map, so I think Antonio's idea of the bloom
filter still makes sense.
Re guava: let's please not introduce this - if we require something from that
lib, just embedd the single class you need, but I definitely don't want this
lib as an OSGi bundle
Long startup time with many vanityPath
--
Key: SLING-3290
URL: https://issues.apache.org/jira/browse/SLING-3290
Project: Sling
Issue Type: Improvement
Components: ResourceResolver
Reporter: Antonio Sanso
Assignee: Antonio Sanso
Labels: vanity
Attachments: SLING-3290-patch.txt, 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.2#6252)
[jira] [Commented] (SLING-3290) Long startup time with many vanityPath
[
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14085852#comment-14085852
]
Bertrand Delacretaz commented on SLING-3290:
FWIW I'm fine about embedding the relevant Guava (or other) code instead of
having to install its bundle. What I object to is creating our own (or
copy/pasted) bloom filter implementation, especially if there are no automated
tests for it ;-)
Long startup time with many vanityPath
--
Key: SLING-3290
URL: https://issues.apache.org/jira/browse/SLING-3290
Project: Sling
Issue Type: Improvement
Components: ResourceResolver
Reporter: Antonio Sanso
Assignee: Antonio Sanso
Labels: vanity
Attachments: SLING-3290-patch.txt, 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.2#6252)
[jira] [Commented] (SLING-3290) Long startup time with many vanityPath
[
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14085969#comment-14085969
]
Antonio Sanso commented on SLING-3290:
--
[~cziegeler] I am afraid is not as easy as embedding one single Guava file for
the BloomFilter. At the sight [0] contains many other dependencies.
[~bdelacretaz] apologies if I did not include unit test for the BloomFilter in
my patch (they do exists though). I will include in my next, more precise patch.
[0]
http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/hash/BloomFilter.html
Long startup time with many vanityPath
--
Key: SLING-3290
URL: https://issues.apache.org/jira/browse/SLING-3290
Project: Sling
Issue Type: Improvement
Components: ResourceResolver
Reporter: Antonio Sanso
Assignee: Antonio Sanso
Labels: vanity
Attachments: SLING-3290-patch.txt, 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.2#6252)
[jira] [Commented] (SLING-3290) Long startup time with many vanityPath
[
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14085974#comment-14085974
]
Bertrand Delacretaz commented on SLING-3290:
@asanso, ok, if there's an automated test I'm ok with integrating that code,
thanks!
Long startup time with many vanityPath
--
Key: SLING-3290
URL: https://issues.apache.org/jira/browse/SLING-3290
Project: Sling
Issue Type: Improvement
Components: ResourceResolver
Reporter: Antonio Sanso
Assignee: Antonio Sanso
Labels: vanity
Attachments: SLING-3290-patch.txt, 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.2#6252)
[jira] [Commented] (SLING-3290) Long startup time with many vanityPath
[
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14084452#comment-14084452
]
Bertrand Delacretaz commented on SLING-3290:
These comments might not be relevant at the current proof of concept level,
feel free to keep them for later ;-)
IIUC you are using a Bloom filter to keep the number of queries down, until the
vanityPath cache is ready?
Sounds like a good idea, but somewhat risky if for some reason the Bloom filter
data becomes inconsistent - this is similar to content repository indexes in
the end, that might need to be rebuilt if they get out of sync. Storing the
filter data in the content repository would probably help, if it is updated
atomically.
Also, updateBloomFilter() might become a bottleneck when importing lots of
content that includes vanity paths, it probably needs to be asynchronous.
I'd much prefer reusing an existing Bloom filter implementation than building
our own - it looks like Guava has one at
http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/hash/BloomFilter.html
Long startup time with many vanityPath
--
Key: SLING-3290
URL: https://issues.apache.org/jira/browse/SLING-3290
Project: Sling
Issue Type: Improvement
Components: ResourceResolver
Reporter: Antonio Sanso
Assignee: Antonio Sanso
Labels: vanity
Attachments: SLING-3290-patch.txt, 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.2#6252)
[jira] [Commented] (SLING-3290) Long startup time with many vanityPath
[
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14084463#comment-14084463
]
Antonio Sanso commented on SLING-3290:
--
[~bdelacretaz] thanks a lot for your comments. They are actually really good
points.
About Guava is it already used somewhere else in Sling?
regards
antonio
Long startup time with many vanityPath
--
Key: SLING-3290
URL: https://issues.apache.org/jira/browse/SLING-3290
Project: Sling
Issue Type: Improvement
Components: ResourceResolver
Reporter: Antonio Sanso
Assignee: Antonio Sanso
Labels: vanity
Attachments: SLING-3290-patch.txt, 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.2#6252)
[jira] [Commented] (SLING-3290) Long startup time with many vanityPath
[
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14084496#comment-14084496
]
Bertrand Delacretaz commented on SLING-3290:
So far I see Guava just in performance/base/pom.xml
Long startup time with many vanityPath
--
Key: SLING-3290
URL: https://issues.apache.org/jira/browse/SLING-3290
Project: Sling
Issue Type: Improvement
Components: ResourceResolver
Reporter: Antonio Sanso
Assignee: Antonio Sanso
Labels: vanity
Attachments: SLING-3290-patch.txt, 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.2#6252)
[jira] [Commented] (SLING-3290) Long startup time with many vanityPath
[
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14084569#comment-14084569
]
Antonio Sanso commented on SLING-3290:
--
[~fmeschbe] thanks a lot for your comment.
bq. full-work-on-update.
just to be sure. Did you follow the update of MapEntries done in SLING-3505.
The full-work-on-update is not there anymore :)
About the /etc/map the things that doesn't make me eager of this solution is
the full duplication of the content (namely the same information is maintained
completely in two location) and the problem to keep those on sync. E.g. what
would happen if I manually delete one vanity path entry from etc/map :S ?
Long startup time with many vanityPath
--
Key: SLING-3290
URL: https://issues.apache.org/jira/browse/SLING-3290
Project: Sling
Issue Type: Improvement
Components: ResourceResolver
Reporter: Antonio Sanso
Assignee: Antonio Sanso
Labels: vanity
Attachments: SLING-3290-patch.txt, 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.2#6252)
[jira] [Commented] (SLING-3290) Long startup time with many vanityPath
[
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14084584#comment-14084584
]
Felix Meschberger commented on SLING-3290:
--
bq. Did you follow the update of MapEntries done in SLING-3505. The
full-work-on-update is not there anymore
Perfect.
bq. About the /etc/map the things that doesn't make me eager of this solution
is the full duplication of the content (namely the same information is
maintained completely in two location) and the problem to keep those on sync.
E.g. what would happen if I manually delete one vanity path entry from etc/map
:S ?
Yes, there is duplication. But we can solve that dilemma in that we declare
the {{/etc/map}} content as being the canonical content and the
sling:vanityPath properties spread around the content to be hints. As I said
vanity paths are really special and should be treated with extreme care. And so
IMHO it is perfectly valid to make it harder to manage them and to be able to
impose processes to update vanity paths. Also {{/etc/map}} is (or should be)
locked down, so that it cannot easily be tampered with.
Long startup time with many vanityPath
--
Key: SLING-3290
URL: https://issues.apache.org/jira/browse/SLING-3290
Project: Sling
Issue Type: Improvement
Components: ResourceResolver
Reporter: Antonio Sanso
Assignee: Antonio Sanso
Labels: vanity
Attachments: SLING-3290-patch.txt, 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.2#6252)
[jira] [Commented] (SLING-3290) Long startup time with many vanityPath
[
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14084601#comment-14084601
]
Antonio Sanso commented on SLING-3290:
--
ok let's assume go with the /etc/map duplication.
Well then I am not sure traversing /etc/map is really so faster than traversing
a query result set, namely the slow startup time behavior might still be
there
Long startup time with many vanityPath
--
Key: SLING-3290
URL: https://issues.apache.org/jira/browse/SLING-3290
Project: Sling
Issue Type: Improvement
Components: ResourceResolver
Reporter: Antonio Sanso
Assignee: Antonio Sanso
Labels: vanity
Attachments: SLING-3290-patch.txt, 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.2#6252)
[jira] [Commented] (SLING-3290) Long startup time with many vanityPath
[
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14054905#comment-14054905
]
Antonio Sanso commented on SLING-3290:
--
added performance test in rev. r1608751
Long startup time with many vanityPath
--
Key: SLING-3290
URL: https://issues.apache.org/jira/browse/SLING-3290
Project: Sling
Issue Type: Improvement
Components: ResourceResolver
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.2#6252)
[jira] [Commented] (SLING-3290) Long startup time with many vanityPath
[
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027043#comment-14027043
]
Antonio Sanso commented on SLING-3290:
--
I am out of office, back on June 22.
regards
antonio
Long startup time with many vanityPath
--
Key: SLING-3290
URL: https://issues.apache.org/jira/browse/SLING-3290
Project: Sling
Issue Type: Improvement
Components: ResourceResolver
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.2#6252)
[jira] [Commented] (SLING-3290) Long startup time with many vanityPath
[
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14018699#comment-14018699
]
Thomas Mueller commented on SLING-3290:
---
I assume vanity path information needs to be available fully in memory, always.
Right?
Could Sling cache the vanity paths information from time to time in one node,
as a binary? Kind of like a precompiled header. That binary would need to be
removed (or marked as invalid) whenever vanity paths are modified. To avoid
rapid re-writing of that binary when vanity paths are changed, it should only
be stored once per minute or so. An observation listener could probably take
care of that (to update the in-memory structure at runtime, and to remove the
outdated binary, and write the new binary from time to time).
Long startup time with many vanityPath
--
Key: SLING-3290
URL: https://issues.apache.org/jira/browse/SLING-3290
Project: Sling
Issue Type: Improvement
Components: ResourceResolver
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.2#6252)
[jira] [Commented] (SLING-3290) Long startup time with many vanityPath
[
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14018727#comment-14018727
]
Antonio Sanso commented on SLING-3290:
--
thanks [~tmueller] this sounds reasonable. A valid alternative would be to use
a Bloom filter
Long startup time with many vanityPath
--
Key: SLING-3290
URL: https://issues.apache.org/jira/browse/SLING-3290
Project: Sling
Issue Type: Improvement
Components: ResourceResolver
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.2#6252)
[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)
[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)
