Delving into what happens when you `import torch`

Lezcano · October 25, 2023, 5:14pm

Put up a stack of PRs remove hte import-time dependency on SymPy:

github.com/pytorch/pytorch

Do not import sympy within torch._prims_common

pytorch:gh/Lezcano/243/base ← pytorch:gh/Lezcano/243/head

opened 04:58PM - 25 Oct 23 UTC

lezcano

+128 -36

Stack from [ghstack](https://github.com/ezyang/ghstack) (oldest at bottom): * #1…12038 * #112037 * #112036 * #112035 * __->__ #112034 This is the first of a few PRs that avoid importing SymPy at import time. The pitch here is that we (almost!) do not have SymPy on our API, so this should be feasible. This should speed-up torch imports by a good 15% as per https://dev-discuss.pytorch.org/t/delving-into-what-happens-when-you-import-torch/1589 In this PR we just move a few global imports into local imports.

Topic		Replies	Views
A TorchDynamo trace time ablation study compiler	0	640	March 22, 2024
Tracing with Primitives: Update 0 compiler	17	8694	September 26, 2022
Embrace tensor subclass as a Python device registration API hardware-backends	5	763	March 28, 2025
What (and Why) is __torch_dispatch__? frontend API	3	16111	July 2, 2024
State of PyTorch core: September 2021 edition frontend API	1	9527	September 21, 2021

Delving into what happens when you `import torch`

Related topics