[jbosstools-issues] [JBoss JIRA] (JBTIS-1077) duplicate entries in devstudio integration stack discovery sites == slower performance loading the site's metadata & crossed streams (stable in the development site)

[Andrej Podhradsky (JIRA)]

     [ https://issues.jboss.org/browse/JBTIS-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrej Podhradsky updated JBTIS-1077:
-------------------------------------
    Attachment: fixed-devstudio-is.png


> duplicate entries in devstudio integration stack discovery sites == slower performance loading the site's metadata & crossed streams (stable in the development site)
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBTIS-1077
>                 URL: https://issues.jboss.org/browse/JBTIS-1077
>             Project: JBoss Tools Integration Stack
>          Issue Type: Bug
>          Components: distribution
>    Affects Versions: 10.2.0.GA
>            Reporter: Nick Boldt
>            Assignee: Paul Leacu
>            Priority: Minor
>             Fix For: 10.2.0.GA
>
>         Attachments: dupe-entries-in-devstudio-is-update-sites-slower-performance.png, fixed-devstudio-is.png
>
>
> With p2 browser, I had a look at the nested/child sites in the devstudiois discovery sites:
> As you can see, both https://devstudio.redhat.com/10.0/stable/updates/integration-stack/discovery/ and https://devstudio.redhat.com/10.0/development/updates/integration-stack/discovery contain references to the latest devstudio is update site and related target platform, 10.2.0.GA. 
> However, since the stable and update sites for devstudio itself ALSO contain these URLs, you've added the same content twice, resulting in 2x the metadata load time for those sites.
> And actually, the problem is worse since you've crossed the streams - there's devstudio IS *STABLE* in the devstudio IS *DEVELOPMENT* site.
> !dupe-entries-in-devstudio-is-update-sites-slower-performance.png|thumbnail! 
> (Admittedly in this case the content is the same... but in theory, you could have 10.3.0.Beta2 content on the development site, and you'd force users to load the 10.2.0.GA content as well, just to then have p2 determine which version was the latest.)



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)