We have an AIR app, which mostly provides an AIR browser wrapper for our Web app. The Web app consists of AJAX and embedded Flash. The performance difference of the AIR browser versus a typical browser (Firefox, Chrome, etc.) is huge! To compare Wep apps performance:
How can this be tuned? Is there a reason that the AIR browser doesn't use as much RAM? Is there a reason that it's using more CPU? Are the two related?
That is a big difference in performance. I'm going to forward this along to our WebKit team but they'll probably need sample code or a test app that will help illustrate the problem. Do you mind opening a new bug on this issue and either attaching the code/sample to the bug report or emailing it to me at firstname.lastname@example.org?
Looks like it's definitely not just our implementation of the AIR browser. I tried another one and on a graphics intensive website. We could go from 2 seconds in a Chrome / Firefox to 10-15 seconds in AIR browser. This makes normally responsive apps hard for users to work with.
Nobody got back to us about this problem report yet: https://bugbase.adobe.com/index.cfm?event=bug&id=2958614.
Anyone hear anything on this? I've just completed months of development on an HTML application wrapped by Adobe Air 2.7 and it is so slow, I cannot continue trying to demo the software to my customer.
The amount of CPU used just to hover around in my app causes the machine to take a serious dump.
I'd like to confirm Oscar's findings on OS differences. We also experience a lot fewer problems in Mac OS X. But Win 7 or Win XP are both quite bad. Win XP additionally has another problem with a Flash app that's embedded in our web app.
Your issues sound identical to mine. Since a large number of us developers have moved to the Mac, I suspect the scope of this problem isn't even as obvious as it should be. I for one am in hot water if I cannot diagnose and resolve these Windows-specific issues in short order.
Off to find Adobe Air debugging tools a la Google Chrome's Inspect Element dev tools.
@Bringster, @bradleford2 -
MS Windows still is the dominant OS on client machines, and for the Adobe AIR Team to overlook these performance issues in AIR 3.0 on Windows is totaly UNBELIEVABLE.
The confusing thing is, test-running my app in AIR from within Dreamweaver (in my Windows 7 dev machine) DOES NOT show the performance issues I see when I run it as an installed AIR app on the same Windows 7 machine (with 12G RAM !!!).
I'm now developing an application in Windows XP to test a theory about the use of jQuery in Adobe air...I am going to focus on a minimalistic example using jQuery vs onmouseover to see if there are issues using jQuery based on Air's implementation of WebKit...
I have not had much luck resolving this through any edits to my application.
Please, anyone following this thread, go to the bug reported here and add your vote: https://bugbase.adobe.com/index.cfm?event=bug&id=2958614
Any news? This is HUGE issue for us.
We may have to change the system requirements of our AIR application and remove Windows compatibility off the list which would be a big loss.
Majority of our software´s target group uses windows.
@Petteri_Paananen, I do share your concerns, and did have one of my worst fears realized yesterday when a potential client decided not to hire me when I disclosed that we may have to wait for Adobe AIR's next runtime release for performance issues on Windows to be resolved by Adobe.
When he asked when it will be, I couldn't give him any definitive answer. It really is so frustrating (an understatement).
Please go to the bugbase URL given in the previous post to enter your vote for this bug. I guess that's all we can do for now.
Thanks for the attention Chris.
This performance issue is such a downer. I hope the Webkit team can offer some temporary workarounds while we await a more permanent resolution, hopefully in the next runtime and/or SDK release, whichever is the source of the problem.
Please let us know immediately about any info related to this.
Hi guys, I see everyone stopped posting on this thread months ago, did you guys find any way to improve the smoothness on the jquery animations in windows? any help would be appreciated. thanks.
I'd like to recommend you cast a vote for this bug:
I can't overstate how major this issue is for HTML/CC/JS based Air applications as a whole. How come that the Air Webkit implementation is so much slower than other Webkit implementations? Is it rendered through a Flash Player instance? If so, would it be possible in any way to override this? Has anyone found any hacks except not using inset box shadow that would possibly bring up the perceived performance of HTML/CSS/JS based content in Adobe AIR desktop app? Has anyone found a viable alternative to using Adobe AIR?
I am thankful for any answers and ofcourse hoping that Adobe will address this issue - the AIR platform is SO good in many other ways but the Webkit performance makes it a non-starter for many situations.