Gelmiş geçmiş en büyük porno sitemiz olan 2pe de her zaman en kaliteli pornoları sunmayı hedefledik. Diğer video sitemiz olan vuam da ise hd porno ağırlıklı çalışmalara başladık.

  1. #1
    Ext User
    Join Date
    Sep 2009
    Posts
    8
    Vote Rating
    0
    extjs@intelliware.ca is on a distinguished road

      0  

    Default GXT Performance Issues

    GXT Performance Issues


    Hi All,

    We are working on a rather complex system using GXT. While everything works great on FF, IE (especially IE6) is a different story (looking at more than 10 seconds until the browser renders the page).

    I understand that one of the main reasons is DOM manipulation which is a disaster under IE6 (See http://www.quirksmode.org/dom/innerhtml.html).

    This can be thought to be a generic problem of a front-end Javascript framework (i.e. GWT) but a simple code (see below) that executes the same functionality proofs otherwise. In fact, under IE6 - getSomeGWT() takes 400ms while getSomeGXT() takes 4 seconds. That's a x10 factor which makes a huge different for the user experience !!!


    Code:
        private HorizontalPanel getSomeGWT() {
            HorizontalPanel pointsLogoPanel = new HorizontalPanel();
            for (int i=0; i<350; i++) {
                HorizontalPanel innerContainer = new HorizontalPanel();
                innerContainer.add(new Label("some GWT text"));
                pointsLogoPanel.add(innerContainer);
            }
            return pointsLogoPanel;
        }
    
        private LayoutContainer getSomeGXT() {
            LayoutContainer pointsLogoPanel = new LayoutContainer();
            pointsLogoPanel.setLayoutOnChange(true);
            for (int i=0; i<350; i++) {
                LayoutContainer innerContainer = new LayoutContainer();
                innerContainer.add(new Text("just some text"));
                pointsLogoPanel.add(innerContainer);
            }
            return pointsLogoPanel;
        }
    So to solve/mitigate the issue one would need to -
    a. Reduce the number of DOM manipulations; or
    b. Replace them with innerHTML.

    AFAIK, (a) is simply a side effect of using GXT and (b) is only possible with UiBinder which isn't supported yet by GXT.

    Any ideas?

    Thanks in advance!

  2. #2
    Software Architect
    Join Date
    Sep 2007
    Posts
    13,971
    Vote Rating
    132
    sven is a glorious beacon of light sven is a glorious beacon of light sven is a glorious beacon of light sven is a glorious beacon of light sven is a glorious beacon of light sven is a glorious beacon of light

      0  

    Default


    Who said that using uibinder makes everything using innerHtml?

    You better read again what uibinder is doing when using widgets.

  3. #3
    Ext User
    Join Date
    Sep 2009
    Posts
    8
    Vote Rating
    0
    extjs@intelliware.ca is on a distinguished road

      0  

    Default


    Thanks for the quick reply!

    What I meant is that UiBinder will consume the HTML specified in the template and set it using innerHtml (See UiBinderUtil.fromHtml).

    Anyway, my question is why is getSomeGXT() ten time slower than getSomeGWT()? And how can we solve this?

  4. #4
    Software Architect
    Join Date
    Sep 2007
    Posts
    13,971
    Vote Rating
    132
    sven is a glorious beacon of light sven is a glorious beacon of light sven is a glorious beacon of light sven is a glorious beacon of light sven is a glorious beacon of light sven is a glorious beacon of light

      0  

    Default


    What I meant is that UiBinder will consume the HTML specified in the template and set it using innerHtml (See UiBinderUtil.fromHtml).
    Yes, IF you specify html, than it is doing it. GXT is doing the same if you specify html.I dont understand this argument in your context.


    GXT layoutsystem works different and far more powerfull. That is why it is slower. We are looking in improvements for GXT3

Thread Participants: 1

Tags for this Thread