1. #1
    Sencha User
    Join Date
    May 2009
    Posts
    91
    Vote Rating
    0
    AndreKR is on a distinguished road

      0  

    Default Overall Performance

    Overall Performance


    The overall performance impact of 4.1 is not as good as I hoped for.

    Here's an example from an app of ours. Doubleclicking a grid row opens a new Ext.window.Window with a four-tab tabpanel with a few grids:

    With ExtJS 4.02b that takes about 1760 ms:

    2011-10-25_1513.jpg


    ExtJS 4.0.7 brings it down to about 1060 ms:

    2011-10-25_1516.jpg


    With ExtJS 4.1 it's still about 863 ms:

    2011-10-25_1518.jpg


    In all cases the provided ext-all.js was used. The values varied by about 50 ms per individual test.

  2. #2
    Sencha - Senior Forum Manager mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    35,704
    Vote Rating
    750
    mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute

      0  

    Default


    Was Ext.window.Window already loaded when you created it?
    Mitchell Simoens @SenchaMitch
    Sencha Inc, Senior Forum Manager
    ________________
    Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
    https://github.com/mitchellsimoens

    Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/

    Need more help with your app? Hire Sencha Services services@sencha.com

    Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!

    When posting code, please use BBCode's CODE tags.

  3. #3
    Sencha User
    Join Date
    May 2009
    Posts
    91
    Vote Rating
    0
    AndreKR is on a distinguished road

      0  

    Default


    Yes, actually I did the same doubleclick several times before (even with timeline recording enabled) to ensure that Chrome has everything cached.

  4. #4
    Ext JS Premium Member Sébastien.Volle's Avatar
    Join Date
    Apr 2011
    Location
    Grenoble, France
    Posts
    70
    Vote Rating
    0
    Sébastien.Volle is on a distinguished road

      0  

    Default


    I don't know, a ~20% improvement is not to be sneezed at in my book.
    A floating window with 4 tab panels and "a few" grids is a fairly complex layout, so a 800ms rendering time sounds pretty good to me.
    aka Seboss

  5. #5
    Sencha - Ext JS Dev Team dongryphon's Avatar
    Join Date
    Jul 2009
    Posts
    1,229
    Vote Rating
    114
    dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all

      0  

    Default


    Can you post an example that mimics what you are doing? Ideally just an html file with script block that presents a button to display the window. Also, it would be important to accurately match where you are auto sizing in your real app because auto sizing entails extra measurements and potentially reflows.
    Don Griffin
    Ext JS Development Team Lead

    Check the docs. Learn how to (properly) report a framework issue and a Sencha Cmd issue

    "Use the source, Luke!"

  6. #6
    Sencha Premium Member
    Join Date
    Sep 2011
    Posts
    48
    Vote Rating
    1
    stahlman is on a distinguished road

      0  

    Default


    @Sebastien - I think you're missing the point here: keep in mind that for many developers, the performance of 4.0 was completely unacceptable - not even close to usable on certain platforms - thus, it should not be taken as the baseline for comparison... While in the abstract, a 20% improvement sounds good, if the thing being improved needs an order of magnitude improvement, 20% seems almost insignificant...

  7. #7
    Ext JS Premium Member Sébastien.Volle's Avatar
    Join Date
    Apr 2011
    Location
    Grenoble, France
    Posts
    70
    Vote Rating
    0
    Sébastien.Volle is on a distinguished road

      0  

    Default


    Maybe Andre should make its expectations a little clearer then. What's *good*?

    I skipped Ext JS 3 altogether so I have no point of comparison between 3.x and 4.0.
    However, I've been working with Ext JS 2.0 for years and 4.0 since the first PR, and I never ran into any situation that makes an application usable. As far as my needs go, a 20% boost is a welcome improvement.
    Granted, IE7/8 are not in my target browsers.

    Did the affected applications you mention really performed so much better with Ext JS 3.x?
    The kind of composition AndreKR describes in the OP sound a bit over the top to me. I'm not sure a window with tabs and several grids would perform that well even on a native widget toolkit :P

    I don't mean to be confrontational or too supportive of Sencha, but I sometime wonder if people just don't demand way too much from Ext JS, which with all its qualities, is still *just* a fancy Javascript/DOM toolkit.

    EDIT: ok, if that benchmark is to be taken seriously, there *does* seem to be quite a performance gap between Ext JS 3 and 4: http://www.sencha.com/forum/showthread.php?152386-IE-Performance-Browser-Benchmarks

    I
    begin to understand where all the embarassment comes from.
    aka Seboss

  8. #8
    Sencha User
    Join Date
    May 2009
    Posts
    91
    Vote Rating
    0
    AndreKR is on a distinguished road

      0  

    Default


    @stahlman That was exactly what I meant, thanks for typing it for me.

    I put together a testcase by removing everything that requires data access while maintaining the layout complexity where possible. It's not exactly a single html file, but I got it down to 3 js-files for the different window types.

    Here it is:
    https://s3-eu-west-1.amazonaws.com/c...case/index.htm

    Just doubleclick lines to open additional windows. You will see that opening the window and even switching between tabs is quite slow.

  9. #9
    Ext JS Premium Member Sébastien.Volle's Avatar
    Join Date
    Apr 2011
    Location
    Grenoble, France
    Posts
    70
    Vote Rating
    0
    Sébastien.Volle is on a distinguished road

      0  

    Default


    I get 350ms average to open the tabs window and ~200ms when switching tabs, using Chromium 15.
    My machine is hardly a beast, how come I get such lower timings than you do?
    aka Seboss

  10. #10
    Sencha User
    Join Date
    May 2009
    Posts
    91
    Vote Rating
    0
    AndreKR is on a distinguished road

      0  

    Default


    Hm, interesting. I can't explain.

    According to Chrome's timeline, switching between tabs consumes about 280 ms, mainly for painting.

    For the tests I used Chrome 15.0.874.106 on an "AMD Athlon 64 X2 4000+ 2.10 GHz".

film izle

hd film izle

film sitesi

takipci kazanma sitesi

takipci kazanma sitesi

güzel olan herşey

takipci alma sitesi

komik eğlenceli videolar