-
-
Notifications
You must be signed in to change notification settings - Fork 560
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.
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
Mediapipe facemesh tfjs #36
Comments
Does the already committed model not fit your needs? |
I tried it for mobile browser for medium/low level devices with decent gpu but got only around 5-6Fps (Webgl backend) . Can you tell what optimization you did in this tfjs model and tfjs facemesh has recently updated with iris support which droped its performance by 5-7fps also. |
I am testing on https://www.devicespecifications.com/en/model/8d2f4cea |
Hmmm. There doesn't seem to be any significant difference in the performance of your device and mine. Have you tried the following demo? |
Yes, i tried this only. Getting 5FPS. |
I generated and committed a TFJS model of Float16, hoping that the GPU would be used effectively. @terryky Does your FaceMesh example program use the Float32 model? Have you tried the Float16 model and have you ever tried it? I don't know if it will improve my performance. |
From the network calls, it looks like this demo |
Yes, the facemesh sample app simply uses mediapipe original tfjs model. @gauravgola96 |
@terryky @PINTO0309 Since you have used the original mediapipe tfjs model I tested https://storage.googleapis.com/tfjs-models/demos/facemesh/index.html which is official demo with predicted iris off. Can I use the quantized model (float 16 ) version in your demo project somehow? |
I suspect that using the fp16 model will not improve performance because I have tried fp16 model in the tensorflow lite environment but I did not see distinguish performance improvement. tflite port is here: |
Any plans for optimization for mobile browsers. Or tfjs model provided in the repo will work.
The text was updated successfully, but these errors were encountered: