8000 How to test the real FPS in my browser?(Chrome or Firefox) · Issue #9 · openstf/minicap · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

How to test the real FPS in my browser?(Chrome or Firefox) #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
Tierney0115 opened this issue Nov 6, 2015 · 6 comments
Closed

How to test the real FPS in my browser?(Chrome or Firefox) #9

Tierney0115 opened this issue Nov 6, 2015 · 6 comments

Comments

@Tierney0115
Copy link

I searched the solution online but did not find a way to do this. How do you test the FPS to get the result 30-40 or 10-20? Thanks.
@Tierney0115
Copy link
Author

By the way I am using STF and want to get the real FPS in time. Thanks.

@gunta
Copy link
Member
gunta commented Nov 6, 2015

We had this feature before, we'll add it back

@sorccu
Copy link
Member
sorccu commented Nov 6, 2015

There used to be an FPS counter in the STF UI. Basically the FPS reported by STF was the speed at which the browser could receive and render frames. However, it's currently difficult to measure, since on newer Android versions we don't read a frame at all if there's no change on the screen. So most of the time it would probably show <1 FPS.

For one frame, all of this needs to happen:

  1. Android notifies us there's a new frame (fast)
  2. We lock the new frame (fast)
  3. The frame is converted to JPEG (slow)
  4. The JPEG data is sent via the ADB USB connection (slow)
  5. Our Node.js application receives the data (fast)
  6. The Node.js application sends the frame data over via WebSocket (fast)
  7. The browser receives the data (fast)
  8. The browser renders the data into <canvas> (speed depends on client specs)

Therefore, the measurable FPS is different at every point. The values mentioned in the README cover all steps and are a reasonable average based on our personal experience.

If you want to measure meaningful FPS, you should write your own application that reads data from the minicap socket over USB as quickly as possible, open an application that's always moving (perhaps a game) and count how many frames it has received.

@Tierney0115
Copy link
Author

@gunta @sorccu
Thank you for your reply. Could you please add this feature back or just email me this piece of code since the FPS is really important for me at this time. Very appreciate.

@sorccu
Copy link
Member
sorccu commented Nov 6, 2015

Perhaps eventually, but I'm too busy to do anything about it right now.

On Friday, 6 November 2015, Tierney0115 notifications@github.com wrote:

@gunta https://github.com/gunta @sorccu https://github.com/sorccu
Thank you for your reply. Could you please add this feature back or just
email me this piece of code since the FPS is really important for me at
this time. Very appreciate.

—
Reply to this email directly or view it on GitHub
#9 (comment).

@Tierney0115
Copy link
Author

OK. I will try to figure it out. Thank you anyway

@qwldcl qwldcl mentioned this issue Apr 24, 2017
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sorccu @gunta @Tierney0115
0