[
https://issues.apache.org/jira/browse/SLING-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-4105:
-----------------------------------
Description:
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.
was:
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.
We should be able to lazily load the data only for the displayed resources.
> 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)
