-
Notifications
You must be signed in to change notification settings - Fork 362
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
Spconv 2.2 Development #380
Comments
Could you clarify what's the level of support for JIT with Spconv 2.2? I intend to train a model in python, but run inference with jit in c++. From what I saw on the Readme, currently spconv 2.x does not support jit. Does it mean jit will be supported in 2.2? |
|
hi,How is the progress of spconv2.2?Looking forward to your great work. |
Spconv 2.x does not support jit,so what inference framework does spconv support? |
same confused about jit. Does it means cannnot convert pytorch to onnx without support of jit ? can anyone give some suggestion the way to deploy spconv? directly add plugin op in torch2tensorrt or any way else? holp for some suggestions. |
Hi @sissini, have u managed to find a solution to deploy the spconv 2.x ? |
Does this method work? Can we directly write a custom plugin in torch2tensorrt for the sparse convolutions? |
Spconv 2.2 development is started. Currently I don't have enough time to develop 2.2 and can't determine a release date.
Spconv 2.2 Core Features
Spconv 2.2 Misc Features
[2021-11-26] Performance issues have been found in RTX 3090/A100 GPUs (they are slower than my 3080 Laptop...). So the int8 task/better tune is moved to spconv 2.3, nvrtc/ampere feature support move to spconv 2.2.
[2022-01-04] spconv 2.2 has been delayed due to busy work and another important project (next-generation framework to speed up develop of all projects include spconv)
[2022-01-20] spconv 2.2 release date: 2022.2.10
If you wants a new feature that can be easily implemented, you can leave a comment for your feature request. (no guarantee to implement)
The text was updated successfully, but these errors were encountered: