-
Notifications
You must be signed in to change notification settings - Fork 20
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
The speed of example in the release (pre) is much slower than the previous method. #22
Comments
Thanks, probably zimg does not efficiently fuse operations. |
@WolframRhodium Hi, i was testing rife v2(bd0ff98) but failed. I'm not sure if I missed sth. |
Does it work if dynamic shapes or faster_dynamic_shapes is disabled? I only have tested the former. |
Failed. |
Though I cannot make it work with dynamic shape, but v2 (Output 16000 frames in 53.22 seconds (300.66 fps)) is much faster than v1 (Output 16000 frames in 68.05 seconds (235.12 fps)). |
Hi, it seems that the edit: replace
the first three warnings (and related source code) confirms the observation, and the last two warnings may be a bug in trt's experimental graph compiler |
@WolframRhodium Hello, I have a question about v2 model. For V1 model, I use 1920x 1088 as the value of opt_shape. Whether should I use the 1920x 1080 instead for V2? |
I think 1920x1080 should be used for V2. |
https://github.com/AmusementClub/vs-mlrt/releases/tag/v13
In my device, "pad first and then crop" (283fps) is faster than "all-in-one" processing (243fps).
1080p_p10
2160p_p10
The text was updated successfully, but these errors were encountered: