You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Will the high CPU usage problem be resolved in the future?
#24067
I'm currently building an ActionScript framework for developing applications and software. It works well on the desktop with Adobe AIR Runtime, but consumes a lot of CPU when running in a browser with Ruffle. A blank swf file can consume around 10% CPU on mid-range laptops. A simple swf file with a little code or a little animation can consume around 15-20% CPU. If runInBackground is enabled and two tabs are open simultaneously, the CPU usage can increase exponentially. For example, A.swf consumes 15% CPU, B.swf consumes 20% CPU. If A.swf and B.swf are open simultaneously, the CPU usage can reach 80%-120%, causing the browser to freeze. Switching between tabs is also laggy.
I've tried many ways to optimize it. But a simple application with a side navigation, a few buttons, and an image display area consistently consumes over 20% CPU when running. Using webGPU for rendering even causes the CPU to jump to 50%.
My question is whether this can be improved in the future? I mean, is there still room for improvement, or has it almost reached its technical limit and cannot be optimized further? Can Ruffle aim to become a highly efficient player (at least on par with Flash Player) for future applications, or is it only intended as an emulator for older content with performance limitations?
I need clarification on this before deciding whether to dedicate significant time (even years) to making my framework compatible with Ruffle, or to pursue a different approach like using Apache Royale.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi!
I'm currently building an ActionScript framework for developing applications and software. It works well on the desktop with Adobe AIR Runtime, but consumes a lot of CPU when running in a browser with Ruffle. A blank swf file can consume around 10% CPU on mid-range laptops. A simple swf file with a little code or a little animation can consume around 15-20% CPU. If runInBackground is enabled and two tabs are open simultaneously, the CPU usage can increase exponentially. For example, A.swf consumes 15% CPU, B.swf consumes 20% CPU. If A.swf and B.swf are open simultaneously, the CPU usage can reach 80%-120%, causing the browser to freeze. Switching between tabs is also laggy.
I've tried many ways to optimize it. But a simple application with a side navigation, a few buttons, and an image display area consistently consumes over 20% CPU when running. Using webGPU for rendering even causes the CPU to jump to 50%.
My question is whether this can be improved in the future? I mean, is there still room for improvement, or has it almost reached its technical limit and cannot be optimized further? Can Ruffle aim to become a highly efficient player (at least on par with Flash Player) for future applications, or is it only intended as an emulator for older content with performance limitations?
I need clarification on this before deciding whether to dedicate significant time (even years) to making my framework compatible with Ruffle, or to pursue a different approach like using Apache Royale.
Thank you!
All reactions