Appium is slooow.

2,205 views
Skip to first unread message

pulsarinfor...@gmail.com

unread,
Aug 6, 2013, 5:49:57 PM8/6/13
to appium-...@googlegroups.com
Anything I can do to increase the speed of Appium?  It takes a full second just to perform a tap operation.  Why is it so slow? 

pulsarinfor...@gmail.com

unread,
Aug 6, 2013, 5:50:45 PM8/6/13
to appium-...@googlegroups.com
I should add this is on a real IOS device - Ipad 2

bootstrap online

unread,
Aug 6, 2013, 6:09:45 PM8/6/13
to pulsarinfor...@gmail.com, appium-...@googlegroups.com
Apple helpfully adds a one second delay. The work around for the
simulator fails on real devices.
https://github.com/facebook/instruments-without-delay
> --
> http://appium.io
> ---
> You received this message because you are subscribed to the Google Groups
> "Appium-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to appium-discus...@googlegroups.com.
> Visit this group at http://groups.google.com/group/appium-discuss.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

David Luu

unread,
Aug 7, 2013, 6:24:10 PM8/7/13
to appium-...@googlegroups.com
I came upon this post recently where the author recommends another tool over Appium for Android automation with one factor being Appium is slow:


I wonder how slow...


On Tuesday, August 6, 2013 2:49:57 PM UTC-7, pulsarinfor...@gmail.com wrote:

bootstrap online

unread,
Aug 7, 2013, 6:44:24 PM8/7/13
to David Luu, appium-...@googlegroups.com
Appium uses uiautomator or selendroid (instrumentation) for Android
automation. I'm not aware of any framework that's faster than the
automation APIs provided by Google.

Spoon is a test runner, not a test framework. It allows you to run
existing instrumentation tests.

Jonathan Lipps

unread,
Aug 7, 2013, 6:55:03 PM8/7/13
to bootstrap online, David Luu, appium-...@googlegroups.com
I'd be curious what the author found to be slow exactly. There is a little bit of overhead for each command that the WebDriver frontend adds, but it's the overhead of local HTTP which is negligent.

Jonathan

Andrew Rymar

unread,
Aug 8, 2013, 4:43:10 PM8/8/13
to appium-...@googlegroups.com, pulsarinfor...@gmail.com
Hmm, it a bit strange because I've just tried to write a simple script with Apple's Automation and it works extremely fast. Even if there are some delay in command execution, it is much less than a second.

среда, 7 августа 2013 г., 1:09:45 UTC+3 пользователь bootstrap online написал:

David Luu

unread,
Aug 12, 2013, 3:17:15 AM8/12/13
to appium-...@googlegroups.com
FYI, this was the blog author's response when I asked for details about Appium slowness:

Appium runs in the cloud on an emulator. Spoon is running locally on real devices, that is a big different. Another thing is, that Appium has only Android 4 as a version for the simulator, no Android 2.3, Android 4.1, 4,2 , 4.3. You can’t choose different screen resolutions and so on. The benchmark I used was my gut feeling :).

Jonathan Lipps

unread,
Aug 12, 2013, 4:15:03 AM8/12/13
to David Luu, appium-...@googlegroups.com
Seems like the author has confused Appium with Sauce Labs

bootstrap online

unread,
Aug 12, 2013, 9:08:35 AM8/12/13
to David Luu, appium-...@googlegroups.com
Appium runs locally on real devices also. Appium in Selendroid mode
supports API 10+.

pulsarinfor...@gmail.com

unread,
Aug 15, 2013, 1:11:39 PM8/15/13
to appium-...@googlegroups.com
So... Nothing can be done to increase the Appium speed on an actual device.  We all just have to live with the 1 second delay introduced by Apple.  And this is by (Apples) design?


On Tuesday, August 6, 2013 2:49:57 PM UTC-7, pulsarinfor...@gmail.com wrote:

bootstrap online

unread,
Aug 15, 2013, 1:13:45 PM8/15/13
to pulsarinfor...@gmail.com, appium-...@googlegroups.com
Ask Apple to improve their testing technology? If there's a better way
then it'll apply to everyone doing iOS testing with UI Automation.

David Luu

unread,
Aug 15, 2013, 3:01:52 PM8/15/13
to appium-...@googlegroups.com, pulsarinfor...@gmail.com
I wonder, there might already be such a bug (or enhancement request) filed to Apple for this. But it would be hard to look up or check status of it until Apple announces the fix/feature. Since Apple has such a secretive closed bug tracking system. Their design actually encourages filing duplicate bugs for them to triage, they must have a lot of time on their hands...

Best place to track Applie bugs, etc. that I know of is here: http://openradar.appspot.com, but it only works well when people who file the bugs file a clone on this other site, and keep the status in sync with the Apple version.
Reply all
Reply to author
Forward
0 new messages