in , , ,

guidoWhy

guidoWhy | python-memes, development-memes, test-memes, loc-memes, threading-memes, lock-memes, performance-memes, IT-memes, ide-memes, bot-memes | ProgrammerHumor.io
python-memes, development-memes, test-memes, loc-memes, threading-memes, lock-memes, performance-memes, IT-memes, ide-memes, bot-memes | ProgrammerHumor.io

Content

Python’s GIL Removal Reveals Second, Stronger GIL Behind It For many years, the Python GIL has been the target of criticism for being a bottleneck in multi-threaded performance. Countless workarounds and promises of its removal have been part of Python development folklore. However, when the Python core development team finally unraveled the notorious lock in the latest experimental build, what lay underneath was beyond anyone’s wild speculations – a secret, second-layer GIL of herculean strength. "Discovering the second GIL not only nullifies all our multi-threading gains but actually puts us at a greater concurrency disadvantage than before." said leading Python contributor Dr. Ana Lepton. " It’s like finding a secret boss in a video game that’s harder than the final boss." Others, however, see it as a challenge. "We’ve faced the first GIL before, and we can face the new one too," ProdrammerHumor.io