Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

API calls are way too slow

See original GitHub issue

The problem

I’m using java-client to do some automation with appium and it seems that it’s way too slow.

For example, RemoteWebElement.click takes 0.4 seconds on average and can take up to 3 seconds sometimes. I’m running on a emulator and it doesn’t make sense that this operation is so slow.

Environment

java client build version or git revision if you use some shapshot:4.1.2
Appium version (or git revision) that exhibits the issue:1.6.0-beta3
Last Appium version that did not exhibit the issue (if applicable):
Desktop OS/version used to run Appium:Linux Mint 18 (Ubuntu 16.04 x64)
Node.js version (unless using Appium.app|exe):
Mobile platform/version under test: Android emulator API 24
Real device or emulator/simulator: Emulator
Appium CLI or Appium.app|exe: CLI (launched using AppiumDriverLocalService)

Link to Appium logs

2016-10-08 05:20:45:796 - info: [HTTP] --> POST /wd/hub/session/2c73a0a8-c376-44ce-96a5-f2ed5d3b1900/element/44/click {"id":"44"}
2016-10-08 05:20:45:797 - info: [MJSONWP] Calling AppiumDriver.click() with args: ["44","2c73a0a8-c376-44ce-9...
2016-10-08 05:20:45:798 - info: [debug] [AndroidBootstrap] Sending command to android: {"cmd":"action","action":"element:click","params":{"elementId":"44"}}
2016-10-08 05:20:45:799 - info: [AndroidBootstrap] [BOOTSTRAP LOG] [debug] Got data from client: {"cmd":"action","action":"element:click","params":{"elementId":"44"}}
2016-10-08 05:20:45:800 - info: [AndroidBootstrap] [BOOTSTRAP LOG] [debug] Got command of type ACTION
2016-10-08 05:20:45:800 - info: [AndroidBootstrap] [BOOTSTRAP LOG] [debug] Got command action: click
2016-10-08 05:20:46:128 - info: [debug] [AndroidBootstrap] Received command result from bootstrap
2016-10-08 05:20:46:129 - info: [MJSONWP] Responding to client with driver.click() result: true
2016-10-08 05:20:46:129 - info: [HTTP] <-- POST /wd/hub/session/2c73a0a8-c376-44ce-96a5-f2ed5d3b1900/element/44/click 200 333 ms - 76 
2016-10-08 05:20:46:130 - info: [AndroidBootstrap] [BOOTSTRAP LOG] [debug] Returning result: {"status":0,"value":true}

Code To Reproduce Issue [ Good To Have ]

element.click();

P.S. Original issue: https://github.com/appium/java-client/issues/484

Issue Analytics

State:
Created 7 years ago
Comments:13

Top GitHub Comments

1reaction

robertluo1949commented, May 16, 2017

@idxn There is no useful about UIAutomator2. We are find that it is cause of animations. My andriod app need launch animations on many pages,howover ,it use many time to excute scripts.

0reactions

lock[bot]commented, Apr 26, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Top Results From Across the Web

Web API call too slow - Stack Overflow

I have an android app that most of its feature consumes an API. My client complained that the retrieving of data from the...

Best Practices to avoiding slow API response time

There are a few optimizations that you can do to avoid slow API responses: · Increasing the number of records returned per page...

Analyzing the Causes of Slow API Call Performance

This dichotomy raises questions that can only be answered through analysis of additional data. For example, is slow Processing Time the primary ......

8 reasons why your API adoption is so slow - TechBeacon

8 reasons why your API adoption is so slow · 1. Documentation has bad design · 2. API provider didn't consider the developer...

TechExchange: Strategies for dealing with slow API responses

The time taken by APIs plays a role in the user experience. One of the ways to handle slow API responses is by...