GP was talking about processes explicitly in comparison to threads, so multiprocessing not multithreading. I believe this was related to their previous comment

GP was talking about processes explicitly in comparison to threads, so multiprocessing not multithreading. I believe this was related to their previous comment about the GIL making true multithreaded performance impossible: > - The Global Interpreter lock - you can't avoid forking processes in order to handle concurrent python code. > - Threads are cheaper than processes. A default java thread carries 2MB overhead, a python process for a typical app can easily be 2GB without very careful memory consideration. And it is indeed true that forking can be much more memory intensive than threading.