A tale of two concurrencies (part 2)

• Autores: David Beazley
• Localización: ;login:: the magazine of USENIX & SAGE, ISSN 1044-6397, Vol. 40, Nº. 4, 2015 (Ejemplar dedicado a: Security and sisadmin), págs. 48-55
• Idioma: inglés
• Texto completo no disponible (Saber más ...)
• Resumen

  • In the previous installment, we dived into some of the low-level details and problems related to Python threads. As a brief recap, although Python threads are real system threads, there is a global interpreter lock (GIL) that restricts their execution to a single CPU core. Moreover, if your program performs any kind of CPU-intensive processing, the GIL can impose a severe degradation in the responsiveness of other threads that happen to be performing I/O.