[jira] [Updated] (SLING-3290) Long startup time with many vanityPath

2014-09-11 Thread Antonio Sanso (JIRA)

 [ 
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Antonio Sanso updated SLING-3290:
-
Fix Version/s: (was: Resource Resolver 1.1.2)

 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] [Updated] (SLING-3290) Long startup time with many vanityPath

2014-08-27 Thread Carsten Ziegeler (JIRA)

 [ 
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler updated SLING-3290:


Fix Version/s: Resource Resolver 1.1.2

 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
 Fix For: Resource Resolver 1.1.2

 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] [Updated] (SLING-3290) Long startup time with many vanityPath

2014-08-06 Thread Antonio Sanso (JIRA)

 [ 
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Antonio Sanso updated SLING-3290:
-

Attachment: SLING-3290-patch-nobloom.txt

attaching new patch going toward the /etc/map approach hinted by [~fmeschbe]. 
To be fair is still a little first step towards SLING-3206 approach but at the 
end of the day was no gain to introduce a bloom filter if we are going to 
replace it soon...

cc [~cziegeler] [~justinedelson] may you please give a look at the patch :) ?

 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] [Updated] (SLING-3290) Long startup time with many vanityPath

2014-08-05 Thread Antonio Sanso (JIRA)

 [ 
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Antonio Sanso updated SLING-3290:
-

Attachment: BloomFilterUtilsTest

attaching test class.
again credit goes to [~tmueller]

 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.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] [Updated] (SLING-3290) Long startup time with many vanityPath

2014-08-05 Thread Antonio Sanso (JIRA)

 [ 
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Antonio Sanso updated SLING-3290:
-

Attachment: BloomFilterUtilsTest.txt

 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.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] [Updated] (SLING-3290) Long startup time with many vanityPath

2014-08-05 Thread Antonio Sanso (JIRA)

 [ 
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Antonio Sanso updated SLING-3290:
-

Attachment: (was: BloomFilterUtilsTest)

 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.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] [Updated] (SLING-3290) Long startup time with many vanityPath

2014-08-04 Thread Antonio Sanso (JIRA)

 [ 
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Antonio Sanso updated SLING-3290:
-

Attachment: SLING-3290-patch.txt

in attachment there is a rough patch in order to show my BloomFilter idea
Credit goes to [~tmueller] for the BloomFilterUtils class that develop this for 
another Apache project...

[~justinedelson] [~cziegeler] may I have your opinion on this.
Just to reiterate .. this is not going to be the final patch but just a 
showcase of the idea...

 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] [Updated] (SLING-3290) Long startup time with many vanityPath

2014-01-23 Thread Antonio Sanso (JIRA)

 [ 
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Antonio Sanso updated SLING-3290:
-

Summary: Long startup time with many vanityPath  (was: Long startup time 
with many vanityPath or alias)

 Long startup time with many vanityPath
 --

 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] [Updated] (SLING-3290) Long startup time with many vanityPath

2014-01-23 Thread Antonio Sanso (JIRA)

 [ 
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Antonio Sanso updated SLING-3290:
-

Component/s: ResourceResolver

 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.1.5#6160)


[jira] [Updated] (SLING-3290) Long startup time with many vanityPath or alias

2013-12-18 Thread Antonio Sanso (JIRA)

 [ 
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] [Updated] (SLING-3290) Long startup time with many vanityPath or alias

2013-12-16 Thread Antonio Sanso (JIRA)

 [ 
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] [Updated] (SLING-3290) Long startup time with many vanityPath or alias

2013-12-16 Thread Antonio Sanso (JIRA)

 [ 
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)