-
Notifications
You must be signed in to change notification settings - Fork 105
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
Why the model predicted so slow on ios device? #58
Comments
@allrightzhu can you share the wechat app for blazeface? |
Yes,which email can I send? |
@allrightzhu can you share it here? If you prefer more secure way, you can create a private github project and add me to the project. Thanks! |
Ok,I invited you. |
@allrightzhu I tried your facemesh demo on iphoneXR the console output indicates around 20ms, blazeface is slower at 30ms |
OK,maybe my iphone6s is too old,I'll try it on more devices. |
@allrightzhu please let us know how did go, thanks. |
I had the similar problem. |
@pyu10055 I also invited you to my project, you can check it out. |
Can you add me to the project too? Thanks! |
Maybe it's not due to tfjs, instead the camera frame difference between iphone and android should be blamed for this. Note that the camera frame resolution on android is a constant 384288, while on iphone, as instruction says, it varies from 480p to 1080p, and 720p (1080720) as default. One useful way to improve is setting the camera resolution low in camera label. Hope it's helpful. |
I am doing a similar project with you,can you please show me your code too? |
JSCore on iOS has no jit. So that in many scenarios V8 on Android is outperformed. Not sure if it's related to this case. |
Can you add me to the project too? Thanks! |
ios mini program run in jsCore without jit |
TensorFlow.js 1.7.0
tfjs-wechat plugin 0.0.9
WeChat 7.0.12
WeChat base API 2.10.4
WeChat IDE v1.02.1911180
I tried to run blazeface model on miniprogram,but I found that it predicted very slow on ios,this is my data about predicted time:
IDE:15ms , android(MI 6): 40ms ios(iphone 6s): 460ms
But if I runed the blazeface model on web,like safari, the predicted time was fast.
The text was updated successfully, but these errors were encountered: