You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2015/02/17 23:51:18 UTC

[jira] [Commented] (SLING-4105) Content Navigator should not read all the jcr_root when initialized

    [ https://issues.apache.org/jira/browse/SLING-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325055#comment-14325055 ] 

Robert Munteanu commented on SLING-4105:
----------------------------------------

* https://svn.apache.org/viewvc?view=revision&revision=r1660526 - added performance tracing
* https://svn.apache.org/viewvc?view=revision&revision=r1660527 - no longer read all children recursively

> Content Navigator should not read all the jcr_root when initialized
> -------------------------------------------------------------------
>
>                 Key: SLING-4105
>                 URL: https://issues.apache.org/jira/browse/SLING-4105
>             Project: Sling
>          Issue Type: Bug
>          Components: IDE
>    Affects Versions: Sling Eclipse IDE 1.0.4
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>             Fix For: Sling Eclipse IDE 1.0.6
>
>
> Currently the {{JcrContentContentProvider}} eagery initialises the data for all of the resources placed under the content sync root. This has a negative effect on the responsiveness of Eclipse, especially since this is all done on the UI thread.
> Two scenarios are especially bad:
> - startup with large project open
> - switching branches for a large project
> This can lock up the UI thread for 20-30 seconds or more. We should be able to lazily load the data only for the displayed resources.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)