20.12.2023, 22:10
(20.12.2023, 22:05)Selur Wrote: Note that I uses TensorRT, which takes quite a while to create a .engine file (will be created for each resolution), but then is quite a bit faster than when using ncnn.
But yes, after building the .engine file, processing ran at ~21fps and for a 3:34.68 clip it took 258.18 seconds (20.79 fps).
Seeint the CUDA and Tensor RT core counts (4060ti vs 4080):
and taking into account that the 4080 uses faster memory, I would have expected it to be ~2.5 faster.Cores 4352 9728
RT Cores 32 76
=> I suspect you didn't use TensorRT, which could explain the speed difference.
Cu Selur
First of indeed Twice as much cores , but 3x times the price (minimum..) the same applies to power consumption LoL
Very true... you've guessed it right.. And i did checked Tensor first then both Tensor + fp16 (for faster .. so it claims but..) ... Indeed it took SOO LONG for the preview, that i thought it would be much slower using Tensor...
But like you said, if it's doing an prep and we users don't know that because we just don't see all the ongoing processes in hybrid you know.. If you put it like that, it might be faster in totality...
but is it now ? Have you add up the time it took to prepare before the actuall encode started ?
Btw... my poor 4060ti encreased to speed 3.04 in the meanwhile
cheers,
TD