Skip to main content
Jun 7, 2018 1:51 PM UTC
Answered

Performance Issues in Flash 30.

We are getting reports from users throughout the Scratch (scratch.mit.edu) community of performance issues related to Flash 30. Upon a deeper investigation it seems as if the main event loop is running much more slowly even in simple tests, this may have something to do with hardware (GPU) acceleration, but more investigation is needed. Results of a single benchmark for Chrome on MacOS are included below, but we are seeing the impacts of these across all 200+ million projects shared in the Scratch online community. We have also been able to repro this on Firefox and Safari on MacOS. We will be testing on Windows shortly and will post results here once complete.

Flash Version - 29.0.0.171

Google Chrome (PPAPI)

Macintosh (OSX)

Flash Version - 30.0.0.113

Google Chrome (PPAPI)

Macintosh (OSX)

This topic is closed to new replies. Start a new post to keep the conversation going.
Correct answer
Jun 11, 2018 6:22 PM UTC

Because of the changes by Adobe which increase the cost of `getTimer` and related APIs, we have deployed a patch that resolves the issue by reducing calls to `getTimer` and gets our performance back to where it was before the release of Flash 30 in most instances. If you are curious, details of the patch are available here:

Flash 30 performance changes by cwillisf · Pull Request #1396 · LLK/scratch-flash · GitHub

Timely assistance from Adobe (particularly in narrowing down the source of our problem) was most appreciated.

27 replies

Legend
Jul 15, 2018 12:26 AM UTC

No. Security fix.

Translate
Legend
Jul 13, 2018 3:12 PM UTC

This will not be fixed, it’s not a bug. The 1000 fold slowdown is deliberate.

Translate
Known Participant
Jul 15, 2018 12:17 AM UTC

1000 slow,not bug?!

3

Translate
Robert Mc Dowell
Legend
Jul 15, 2018 12:28 AM UTC

Spectre / Meltdown Mitigations

Same story for javascript

Translate
Participant
Jul 13, 2018 3:05 PM UTC

Hi, Is the getTimer  performance fix in v30.0.0.134?  If not, which version will the fix be in or how do I find out?  Thanks.

Translate
Known Participant
Jul 10, 2018 5:01 AM UTC

hi,but the mobile devices,alos gettimer,slow.

how slove that?

thanks very mush

Translate
_maria_
Legend
Jul 10, 2018 3:00 PM UTC

As mentioned previously, Flash Player is not supported on any mobile devices, as such, there is no workaround to implement on the mobile device.

Translate
Known Participant
Jul 11, 2018 4:58 AM UTC

But the GETTIME function on the phone is also a thousand times slower. Is there a way to solve this?

But the GETTIME function on the phone is also a thousand times slower. Is there a way to solve this?But the GETTIME function on the phone is also a thousand times slower. Is there a way to solve this?

Translate
Known Participant
Jul 10, 2018 4:29 AM UTC

how set EventJitterMicroseconds in android ,and ios,pls ,thanks

h

Translate
_maria_
Legend
Jul 10, 2018 4:43 AM UTC

Flash Player isn't supported on mobile devices, as such, there is no way to configure this setting mobile devices.

Translate
chris.campbell
Legend
Jun 7, 2018 4:08 PM UTC

Thank you for the heads up.  Our team has reproduced the issue and we're now investigating further.

Chris

Translate
chris.campbell
Legend
Jun 7, 2018 10:20 PM UTC

We've made a necessary mitigation for Spectre/Meltdown-style attacks that significantly increases the cost of calls to getTimer() and related APIs (~100us).  This change isn't apparent in most content, but if you're calling getTimer in a tight loop, the impact is pretty pronounced. The best solution is to modify the content to use getTimer() more judiciously.

From our initial investigation into the Scratch codebase, it does appear that getTimer() is being aggressively used.  Can these API calls be reduced?

An alternative would be to set TimerJitterMicroseconds=0 in the system's mms.cfg file, however this is not recommended as it removes the benefit of the additional security mitigation.

Translate
justtryme
Participant
Jun 8, 2018 8:22 AM UTC

getTimer() now works about thousand times slowlier than in earlier vers. of FP. Don't you think it's a bad practice, to reduce performance with exploit fixes.

We would appreciate Adobe to release a fix for getTimer() calls

Translate