<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Gil on wid's blog</title><link>https://wid-blog.github.io/en/tags/gil/</link><description>Recent content in Gil on wid's blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 15 Jun 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://wid-blog.github.io/en/tags/gil/index.xml" rel="self" type="application/rss+xml"/><item><title>Three Concurrency Models — GIL, Virtual Thread, and Goroutine</title><link>https://wid-blog.github.io/en/posts/tech/language/three-concurrency-models/</link><pubDate>Sat, 15 Jun 2024 00:00:00 +0000</pubDate><guid>https://wid-blog.github.io/en/posts/tech/language/three-concurrency-models/</guid><description>CPython&amp;rsquo;s GIL serializes multithreaded execution and pushes work onto multiprocessing or asyncio. Java pinned threads 1:1 to the OS until virtual threads (Java 21) reopened the thread-per-request model. Go shipped with an M:N scheduler from day one. The model you start from decides whether your service goes thread-per-request, reactive, or multiprocess.</description></item></channel></rss>