Replies: 1 comment 1 reply
-
The paper mentions it as a possibility, say if you trace it and optimize the operations it would be possible to fuse it. However in pytorch at that time, there was no such jit tracer. Nowadays you can do jit trace of pytorch modules and while it will not fuse all the operations, it is feasible that in the future onnx or other optimizing jit compilers can do it automatically v |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi everyone! In Jasper paper i found this lines:
But in the jasper block code in nemo, I didn't see this sub-block merging completely into the core. Do I understand correctly that the line "Each sub-block can be fused" means that the operations in the sub-block are fused separately (conv->batch_norm->relu->dropout and conv fused, then the results are returned in batch_norm, which are also fused, etc.), not the entire sub-block?
No attempt is made to completely fused the subblock.
NeMo/nemo/collections/asr/parts/submodules/jasper.py
Lines 974 to 1051 in 5d5c0fb
Can someone help me. I'm thinking, maybe these are some other details responsible for the fusion of the entire sub-block? or does "fused" mean that the subblock consists of "fused" operations like conv and batch norm?
Beta Was this translation helpful? Give feedback.
All reactions