flex-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: Crippling Lag - Windows 10 IE11 - FlashPlayer / IBM ILOG Elixir
Date Sat, 08 Apr 2017 05:03:45 GMT


On 4/7/17, 4:04 AM, "DarrenEvans" <darren.evans@allocatesoftware.com>
wrote:

>I think the staticRenderHandler is a red herring, FTETextField sets event
>listeners up to call that method on every RENDER and ENTER_FRAME so we'd
>expect that to be called all the time.

Yes, if you single step for a while and end up back at debugTickler, then
you saw all of the AS3 running in the frame, and it looks like there isn't
any serious work for it to do.

Of course, if you can also get a debugger on the SWF when it isn't having
the performance problem, you can compare to see if it is running the same
AS3 and rule it out.

I think the next step is to start comparing working vs non-working.
Compare the stage size.  Amount of memory.  Networking configuration.  I
would swear that Flash uses up more cycles on a slower network, but I
don't have definitive proof.

Also, are there any other configuration differences?  Screen depth,
resolution, etc?  Super-high-resolution screens could take more time to
render.

There was also some performance issues related to line drawing.  If you
draw lines with different line-joins, some line-joins because really slow.

In another case I saw, a bug kept a tiny Flash Authoring SWF they were
using for either a wait cursor or some advertising running.

HTH
-Alex


>
>Here are some screenshots that may provide some more insight and make
>things
>a bit clearer from what I'm seeing in Scout.
>
>The first is showing the time line for, logging in, navigating to a really
>basic screen and then leaving it idle. The idle time is the selected
>portion. See the uncategorized "Runtime Overhead" making up pretty much
>all
>the time:
><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fl
>ex-users.2333346.n4.nabble.com%2Ffile%2Fn14991%2FBasic_Idle_Time.png&data=
>02%7C01%7C%7Ce29525ffb3464e48aaae08d47da72cf2%7Cfa7b1b5a7b34438794aed2c178
>decee1%7C0%7C0%7C636271604362597995&sdata=Ah3Kexnd6xb0natn7z8L2jK8eKjwnNRD
>%2BWOgpwOxrPw%3D&reserved=0>
>
>The second is showing the time line for, logging in, navigating to a part
>of
>the system which has our most complicated usage of the ILOG Ganntt
>component, then leaving it idle. Again the idle portion is the selected
>section, notice how much higher the orange section is when in this part of
>the system. Again nearly all time in "Runtime Overhead":
><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fl
>ex-users.2333346.n4.nabble.com%2Ffile%2Fn14991%2FILOG%252520Idle%252520Tim
>e.png&data=02%7C01%7C%7Ce29525ffb3464e48aaae08d47da72cf2%7Cfa7b1b5a7b34438
>794aed2c178decee1%7C0%7C0%7C636271604362597995&sdata=%2FSaKVOT2x8xdoj6PWyE
>Ewd9MD6DA35f5feLzDDtGdEo%3D&reserved=0>
>
>
>
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-users.2333346.n4.nabble.com%2FCrippling-Lag-Windows-10-IE11-FlashPlayer-
>IBM-ILOG-Elixir-tp14958p14991.html&data=02%7C01%7C%7Ce29525ffb3464e48aaae0
>8d47da72cf2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63627160436259799
>5&sdata=FGqDrlEaQeYoCGOT0AsOOgRFnIpQXb4B0PcT1lFfKWA%3D&reserved=0
>Sent from the Apache Flex Users mailing list archive at Nabble.com.

Mime
View raw message