A viable solution for Python concurrency [LWN.net]
Concerns over the performance of programs written in Python are often overstated — for some use cases, at least. But there is no getting around the problem imposed by the infamous global interpreter lock (GIL), which severely limits the concurrency of multi-threaded Python code. Various efforts to remove the GIL have been made over the years, but none have come anywhere near the point where they w
perlthrtut - Tutorial on threads in Perl - Perldoc Browser
CONTENTS NAME DESCRIPTION What Is A Thread Anyway? Threaded Program Models Boss/Worker Work Crew Pipeline What kind of threads are Perl threads? Thread-Safe Modules Thread Basics Basic Thread Support A Note about the Examples Creating Threads Waiting For A Thread To Exit Ignoring A Thread Process and Thread Termination Threads And Data Shared And Unshared Data Thread Pitfalls: Races Synchronizatio
Transactional Memory (II)
Here is an update about the previous blog post about the Global Interpreter Lock (GIL). In 5 months, the point of view changed quite a bit. Let me remind you that the GIL is the technique used in both CPython and PyPy to safely run multi-threaded programs: it is a global lock that prevents multiple threads from actually running at the same time. The reason to do that is that it would have disastro
Demonstration of the effect on data safety when removing Ruby/Python GIL | Merbist
After my recent RubyConf talk and follow up post addressing the Ruby & Python’s Global Interpreter Lock (aka GVL/Global VM Lock). a lot of people asked me to explain what I meant by “data safety”. While my point isn’t to defend one approach or the other, I spent a lot of time explaining why C Ruby and C Python use a GIL and where it matters and where it matters less. As a reminder and as mentioned
[Python-Dev] Reworking the GIL
Antoine Pitrou solipsis at pitrou.net Sun Oct 25 21:22:20 CET 2009 Previous message: [Python-Dev] Buildbot alternate renderings Next message: [Python-Dev] Reworking the GIL Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Hello there, The last couple of days I've been working on an experimental rewrite of the GIL. Since the work has been turning out rather successful (or, at least, n
We need Software Transactional Memory
Hi all. Here is (an extract of) a short summary paper about my current position on Software Transactional Memory as a general tool in the implementation of Python or Python-like languages. Thanks to people on IRC for discussion on making this blog post better (lucian, Alex Gaynor, rguillebert, timonator, Da_Blitz). For the purpose of the present discussion, we are comparing Java with Python when i
Global Interpreter Lock, or how to kill it
People that listened to my (Armin Rigo) lightning talk at EuroPython know that suddenly, we have a plan to remove the Global Interpreter Lock --- the infamous GIL, the thing in CPython that prevents multiple threads from actually running in your Python code in parallel. That's not actually new, because Jython has been doing it all along. Jython works by very carefully adding locks to all the mutab
How to Add CSS Customization to a WordPress Widget | Merbist
Merbist.com is a web that contains a collection of tutorials for making simple applications, android development, and programming languages. Most sidebar widgets on WordPress usually have the same style according to the theme. It’s okay if all the widgets that appear have the same priority or level of importance. However, in reality, some widgets are of higher importance than other widgets, so we
Jabberwocky
MRI Ruby and Rubinius are both blessed with what is called the Global Interpreter Lock. This means that only execute one thread can be executed at a time per VM instance (per CPU core). See also Ilya Grigorik's and Yehuda Katz's article on the subject. This is not entirely a bad thing, since it means C extensions don't have to be thread-safe (thanks Benoit Daloze for the input). And as the wikiped
Ruby gvl-improvement at ruby 1.9.3
The document discusses Ruby's Global VM Lock (GVL) and improvements made in Ruby version 1.9.3. The GVL ensures only one Ruby thread can execute at a time, limiting Ruby's ability to take advantage of multi-core CPUs. Ruby 1.9.3 improves threading performance by releasing the GVL during I/O operations, allowing other threads to run while one thread is blocked on I/O. It also uses POSIX sched_yield
ＫＯＮＡＭＩ、スクエニ、セガ、バンナム、コーエーの大手5社がゲーム開発現場の未来を再び討議
【10月11日】 カプコンブースポート 「モンスターハンター3」など全タイトルが試遊可能 「東京ゲームショウ2008」ＫＯＮＡＭＩイベントレポート PS3/Xbox 360版「悪魔城ドラキュラ」製作決定、 MGO拡張パック第二弾追加情報を発表 「東京ゲームショウ2008」出展メーカー特設サイトリンク集 「東京ゲームショウ2008」記事リンク集 SCEJブースレポート PS3「リトルビッグプラネット」、「Flower」ほかDL専用PS3タイトルその1 (開発者インタビュー付き) マイクロソフトブースレポート サードパーティータイトルを中心に24タイトルをプレイアブル出展 マイクロソフト、東京ゲームショウ2008 Xbox 360スクリーンショット集 セガブース、イベントレポートその1 期待の3プロジェクトの記者発表会を開催! セガブース、イベントレポートそ
マルチコア危機：ScalaとErlangの対立
ブロゴスフィアでは最近Scala対Erlangの議論がややヒートし続けている。マルチコアの世界(参考記事)が訪れようとしている今、いかにマルチコア危機を解決するかが問題になっている。ScalaとErlangはその解決法たらんとしている言語だが、少し違いがある。それぞれのアプローチの長所短所はなんだろうか？ 問題 ムーアの法則はもう通用しない。かつてのようなクロック周波数の向上(リンク)は見込めず、かわりにコアの数を増やそうとしている。今の時代、あなたのノートPCでさえも2つコアを搭載していることだろう。 2つ以上のコアを有効に使うには、アプリケーションが並列処理を意識してないといけない。もしあなたの顧客が8コアのマシンを買ったとしたら、たとえそれをあるアプリケーションの専用マシンにしたとしても、そのアプリケーションがCPU性能の12%しか使えなくてもおかしくない、とあなたは顧客にどうにかし
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
In Search of the Perfect Global Interpreter Lock
NewGIL
The GIL and PyPy