All geek questions in one place

Django Virtualenv Production

Are there any compromises (memory, performance, etc.) when deploying Django in production with virtualenv?

I like how it's all sandboxed and clean, but it seems it can't find any performance information.

Any direction would be nice.

Thanks,

+6
source share
2 answers

There is no natural difference between an env managed by Virtualenv and those who do not use it: just different file system directories and Python paths. In addition, Virtualenv saves our Dev time by providing the sandbox you mentioned, allowing flexible configuration of envs and switching between them on one node, eliminating the sudo requirement ... which, IMO, is a big performance boost.

+8
source

No, I think. I always use virtualenv. Regardless of the location of the packages on disk, all of them must be loaded into memory for the Django process. The tough part is rebuilding the virtual one when you need to recompile python, but I don't see any performance issues at all.

+1
source

Source: https://habr.com/ru/post/913638/

More articles:


All Articles