Bug 255081
| Summary: | On Android Mobiles Speedometer score is giving different score when clicked start test using finger and using Automation keyevents | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | evijaythegr8 <evijaythegr8> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | ap |
| Priority: | P2 | ||
| Version: | Other | ||
| Hardware: | Other | ||
| OS: | Other | ||
evijaythegr8
For SPeedometer Benchmark 2.0.
Score is varying if we run manually and using automation.
Manually if we click START test on http://browserbench.org/Speedometer2.0/, we are getting better score around 160.
The same if we start test by clicking using automation, we are getting around 120.
Automation method includes:
ADb shell input tap coordinates
UIAUtomator click
Perform using getevents.
IS there any mechanism where we can achieve same score as manual, please let us know.
We are facing this issue on all Android Mobiles.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
Is there any chance that the automation keeps using CPU time in the background? This seems like the most likely explanation. Or something about the priority of the automation process.
In any case, I don't think that we'll be able to investigate this issue, because it doesn't have precise steps to reproduce, and also because people just don't have any Android devices.
evijaythegr8
No automation is not having any priority or CPU time in background.
Even if we try with ADb shell input tap x1,y1,x2,y2 also we are getting different scores.
Does any CPU boost is triggered based on Touch Event, which is only caused by manual touch and not with events.
Alexey Proskuryakov
Possibly. You are asking in WebKit Bugzilla, and WebKit doesn't work on Android. So this is an unlikely place to receive advice.
I'm going to close as INVALID, as there is no indication of a Speedometer benchmark issue here.