Hi Alex,

I checked by putting traces to flex and can say that it is around 3 secs.

For royale i realized that the most time consuming part is the browser logging not related with royale.

After closing the browser console it gets around 5-6 secs which is acceptable.

Thanks,
Serkan

14.03.2020 19:48 tarihinde Alex Harui yazdı:

Can you summarize the comparison between Flex and Royale?  I think you are saying the Flex app takes 7 seconds and the Royale takes 14 or 16?

-Alex

*From: *Serkan Taş <[email protected]>
*Date: *Saturday, March 14, 2020 at 12:12 AM
*To: *"[email protected]" <[email protected]>, Alex Harui <[email protected]>
*Subject: *Re: selectionChange of MX ADG is not implemented

It takes around 16 secs to finalize the view display.

According to network view, 2.30 secs of the time consumed is the "rest call" duration.

it takes nearly 14 secs to prepare the view

13.03.2020 20:59 tarihinde Alex Harui yazdı:

    One way we created tests was to add a couple of buttons to the
    app. You make a copy of the result handler and comment out code in
    the original that sets the data provider.  The first button makes
    the server call.  The other runs the code that sets the data provider.

    HTH,

    -Alex

    *From: *Serkan Taş <[email protected]>
    <mailto:[email protected]>
    *Reply-To: *"[email protected]"
    <mailto:[email protected]> <[email protected]>
    <mailto:[email protected]>, "[email protected]"
    <mailto:[email protected]> <[email protected]>
    <mailto:[email protected]>
    *Date: *Thursday, March 12, 2020 at 11:40 PM
    *To: *"[email protected]" <mailto:[email protected]>
    <[email protected]> <mailto:[email protected]>
    *Subject: *Re: selectionChange of MX ADG is not implemented




        It is hard to determine Alex.

        For flex, the grid is populated through a rest service and it
        takes 3 sec to load the grid data of six lines including the
        rest service call. But the flex app is fully loaded by default.

    For Royale;



        with one column custom renderer with 6 columns it gets around
        7 secs to fully load and display for the test case.

        I commented out the custom renderer and it gets around 5.5 secs.

        Needs more investigation. I am going to work on try to
        discover how to measure and improve performance if necessary.

        Thanks,
        Serkan

        13.03.2020 07:53 tarihinde Alex Harui yazdı:

            Try commenting out all of the custom item renderers.  That
            will tell you if the custom renderers are the culprit. I
            don’t know what your production renderers look like, but
            the ones in the test case looked potentially heavy.

            What is the load time in your Flex app?

            -Alex







Reply via email to