A fast, free threading Python
If PEP-703 is accepted, subinterpreters will still be a possible choice for those who think it’ll be easier to manage. … For a (pure) Python developer free threading will be no more dangerous than GIL threading was. It’s only the native extension authors that will need to care (but Cython counts as native). I don’t think that is true. If free threading is possible, the cat will be out of the bag,
Mojoã¯ã€ŒC言語ã®ã‚ˆã†ã«é€Ÿã„Pythonã€ãªã®ã‹ - k0kubun's blog
LLVMã‚„Swiftを作ã£ãŸChris LattnerãŒCEOã‚’ã‚„ã£ã¦ã„る会社ãŒã€Pythonã®ä½¿ç”¨æ„Ÿã¨C言語並ã®æ€§èƒ½ã‚’ä½µã›æŒã¤è¨€èªžã¨ã—ã¦Mojoをアナウンスã—ãŸã€‚ ã¾ã 手元ã§è©¦ã›ã‚‹çŠ¶æ…‹ã§ãƒªãƒªãƒ¼ã‚¹ã•ã‚Œã¦ã¯ã„ãªã„ãŒã€æœ€å¤§35000å€Pythonより速ã„ã¨ã„ã†ã€‚ Mojo🔥 combines the usability of Python with the performance of C, unlocking unparalleled programmability of AI hardware and extensibility of AI models. Also, it's up to 35000x faster than Python 🤯 and … deploys 🎠pic.twitter.com/tjT09U4F80— Modular (@Modular_AI) May
Python 3.11ã®æ–°æ©Ÿèƒ½(ãã®3）関数呼ã³å‡ºã—ã®ã‚¤ãƒ³ãƒ©ã‚¤ãƒ³åŒ– - python.jp
Python 3.11ã§ã¯ã€ãƒ‘フォーマンスãƒãƒ¥ãƒ¼ãƒ‹ãƒ³ã‚°ã®ä¸€ç’°ã¨ã—ã¦ã€Python関数呼ã³å‡ºã—ã®ã‚¤ãƒ³ãƒ©ã‚¤ãƒ³åŒ– ãŒè¡Œã‚ã‚Œã¾ã—ãŸã€‚æ—¢å˜ã®Pythonインタープリタã®ã—ãã¿ã‚’大ãã変更ã™ã‚‹å¤‰æ›´ã§ã™ã®ã§ã€ç°¡å˜ã«è§£èª¬ã—ã¦ãŠãã¾ã™ã€‚ å…ˆã«æ›¸ã„ã¦ãŠãã¾ã™ãŒã€ä»Šå›žè¡Œã‚ã‚ŒãŸã€Œé–¢æ•°å‘¼ã³å‡ºã—ã®ã‚¤ãƒ³ãƒ©ã‚¤ãƒ³åŒ–ã€ã¯ã€C/C++ãªã©ã® inline ã®ã‚ˆã†ã«ã€ãƒ¦ãƒ¼ã‚¶å®šç¾©é–¢æ•°ã‚’呼ã³å‡ºã—å…ƒã§å±•é–‹ã—ã¦ã‚ªãƒ¼ãƒãƒ˜ãƒƒãƒ‰ã‚’削減ã™ã‚‹ã‚‚ã®ã§ã¯ã‚ã‚Šã¾ã›ã‚“。ã¾ãŸã€Schemeãªã©ã«ã‚る末尾å†å¸°ã®æœ€é©åŒ–ã§ã‚‚ã‚ã‚Šã¾ã›ã‚“。 cevalループ¶Pythonインタープリタã¯ã€Python 3.11ã®æ–°æ©Ÿèƒ½(ãã®2） 特殊化é©å¿œçš„インタープリタ ã§è§£èª¬ã—ãŸã‚ˆã†ã«ã€Pythonã®ã‚½ãƒ¼ã‚¹ã‚³ãƒ¼ãƒ‰ã‚’ãƒã‚¤ãƒˆã‚³ãƒ¼ãƒ‰ã¸å¤‰æ›ã—ã€é †æ¬¡å®Ÿè¡Œã—ã¾ã™ã€‚ã“ã®ãƒã‚¤ãƒˆã‚³ãƒ¼ãƒ‰ã‚’実行ã™ã‚‹é–¢æ•°ã¯Pythonインタープリタã®å¿ƒè‡“部ã§ã‚ã‚Šã€CPythonソースツリーã®ãƒ•ã‚¡ã‚¤ãƒ« Python/c
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
HolyJit: A New Hope
tl;dr: We believe there is a safer and easier way of writing a Jit. Current State Today, all browsers’ Jits share a similar design. This design makes extending the language or improving its performance time-consuming and complex, especially while avoiding security issues. For instance, at the time of this writing, our Jit relies upon ~15000 lines of carefully crafted, hand-written assembly code (~
PHP 7ã®ãƒ‘フォーマンスãŒé«˜ã„ç†ç”±
CodeZine編集部ã§ã¯ã€ç¾å ´ã§æ´»èºã™ã‚‹ãƒ‡ãƒ™ãƒãƒƒãƒ‘ーをスターã«ã™ã‚‹ãŸã‚ã®ã‚«ãƒ³ãƒ•ã‚¡ãƒ¬ãƒ³ã‚¹ã€ŒDevelopers Summitã€ã‚„ã€ã‚¨ãƒ³ã‚¸ãƒ‹ã‚¢ã®ç”Ÿãã–ã¾ã‚’ブーストã™ã‚‹ãŸã‚ã®ã‚¤ãƒ™ãƒ³ãƒˆã€ŒDevelopers Boostã€ãªã©ã€ã•ã¾ã–ã¾ãªã‚«ãƒ³ãƒ•ã‚¡ãƒ¬ãƒ³ã‚¹ã‚’ä¼ç”»ãƒ»é‹å–¶ã—ã¦ã„ã¾ã™ã€‚
言語処ç†ç³»ã€€å®šç‚¹è¦³æ¸¬ 2011/12/1
sys = require "sys" fff = (x) -> x + 2 ggg = (x) -> a={} a.p = x a.p t = 0 for i in [0..100000000] t += ggg(i) sys.puts "ttt:#{t}"
In Search of the Perfect Global Interpreter Lock
1. In Search of the Perfect Global Interpreter Lock David Beazley http://www.dabeaz.com @dabeaz October 15, 2011 Presented at RuPy 2011 Poznan, Poland Copyright (C) 2010, David Beazley, http://www.dabeaz.com 1 2. Introduction • As many programmers know, Python and Ruby feature a Global Interpreter Lock (GIL) • More precise: CPython and MRI • It limits thread performance on multicore • Theoreticall
Coders Paradise
In the ever-evolving world of programming, staying ahead of the curve and constantly improving one's skills is crucial. Python, a widely-used and flexible language, offers a multitude of engaging activities that can help programmers level up their abilities and deepen their understanding. From immersive online role-playing games that allow users to code their way through challenges, to coding plat
asm.js
Working Draft — 18 August 2014 Latest version: http://asmjs.org/spec/latest/ Editors: David Herman, Mozilla, <[email protected]> Luke Wagner, Mozilla, <[email protected]> Alon Zakai, Mozilla, <azakai@mozilla.com> Abstract This specification defines asm.js, a strict subset of JavaScript that can be used as a low-level, efficient target language for compilers. This sublanguage effectively describes
ã“ã®ãƒšãƒ¼ã‚¸ã‚’見るã«ã¯ã€ãƒã‚°ã‚¤ãƒ³ã¾ãŸã¯ç™»éŒ²ã—ã¦ãã ã•ã„
Facebookã§æŠ•ç¨¿ã‚„写真ãªã©ã‚’ãƒã‚§ãƒƒã‚¯ã§ãã¾ã™ã€‚
実行時ã®ãƒ‡ãƒ¼ã‚¿åž‹ã®è¡¨ç¾æ‰‹æ³•
2. ã“ã®ã‚¹ãƒ©ã‚¤ãƒ‰ã®ç›®çš„ •  64bit ARMアーã‚テクãƒãƒ£ã®Tagged Pointeræ©Ÿ 能ãŒè©±é¡Œã«ãªã£ãŸ •  よã„機会ãªã®ã§ï¼Œå®Ÿè¡Œæ™‚ã«ãƒ‡ãƒ¼ã‚¿åž‹ã‚’判別㙠るãŸã‚ã®ãƒ‡ãƒ¼ã‚¿è¡¨ç¾ã‚’ã¾ã¨ã‚ã¦ãŠã“ã†ã¨æ€ã£ãŸ •  ホットãªãƒˆãƒ”ックã¨ã„ã†ã‚ˆã‚Šï¼Œå¤§æ˜”ã‹ã‚‰ã®ï¼Œã„ã‚ ã°æ•™ç§‘書的ãªè©±é¡Œã ãŒï¼Œæ•™ç§‘書ã«ã¯ã‚ã‚“ã¾ã‚Š 載ã£ã¦ãªã„ •  手法ã®é¸æŠžã«ã¯GCやメモリ管ç†ã¨ã®ç›¸äº’作 用も絡むã®ã ãŒï¼Œã»ã¼ãƒãƒƒã‚µãƒªçœç•¥ 3. 実行時ã«ãªãœãƒ‡ãƒ¼ã‚¿åž‹ã‚’判別ã™ã‚‹ å¿…è¦ãŒã‚ã‚‹ã®ã‹ï¼Ÿ •  動的型付ã言語 –  変数ã«é™çš„ãªï¼ˆï¼å®Ÿè¡Œå‰ã®ãƒ»ã‚³ãƒ³ãƒ‘イル時ã®ï¼‰åž‹ ãŒä»˜ã„ã¦ã„ãªã„ –  実行ã™ã‚‹ã¾ã§ï¼Œã©ã‚“ãªåž‹ã®ãƒ‡ãƒ¼ã‚¿ãŒå…¥ã‚‹ã‹ã‚ã‹ã‚‰ ãªã„ •  多相型ã¨GC –  æ•´æ•°ã®ãƒªã‚¹ãƒˆã‚‚æ–‡å—列ã®ãƒªã‚¹ãƒˆã‚‚å—ã‘å–れる関数 ã®å¼•æ•°â€¦GCãŒï¼Œãƒã‚¤ãƒ³ã‚¿ã‚’追跡ã™ã‚‹æ‰‹ãŒã‹ã‚Š 4. 実行時ã®åž‹åˆ¤åˆ¥ã®åŸºæœ¬æ“作 •  is_type(x, t) –  データxã®åž‹
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
Java 7 invokedynamic ã®æ¦‚è¦
3. 2 invokedynamic ã¨ã¯ï¼Ÿ • Java 6 ã¾ã§ã® JVM = Java ã®ãŸã‚ã®ä»®æƒ³ãƒžã‚·ãƒ³ • Java 7 ã® JVM = Java + Java 以外ã®è¨€èªžã®ãŸã‚ã®ä»®æƒ³ãƒžã‚·ãƒ³ • invokedynamic 㯠Java 以外ã®è¨€èªžã®ãŸã‚ã« è¿½åŠ ã•ã‚ŒãŸæ–°ã—ã„メソッド呼ã³å‡ºã—命令 4. 3 論点 • Java 6 ã¾ã§ã®å‘¼ã³å‡ºã—命令 – JVM 命令㯠Java ã®ãŸã‚ã«ä½œã‚‰ã‚Œã¦ã„㟠• Java 以外ã®è¨€èªž – æ—¢å˜ã®å‘½ä»¤ã‚»ãƒƒãƒˆã§ã¯ Java 以外ã®è¨€èªžå‡¦ç†ç³»ãŒ 効率的ã«å®Ÿè£…ã§ããªã„ • invokedynamic – æ–°ã—ã„命令㧠Java 以外ã®è¨€èªžã‚‚効率的ã«ãªã‚‹
sunagae.net [軽é‡è¨€èªžå‘ã‘リアルタイムプãƒãƒ•ã‚¡ã‚¤ãƒ© (llprof)]
hg clone http://www.sunaga-lab.com/hgrepos/llprof # 安定版ã¸æ›´æ–° hg update stable # 最新版ã¸æ›´æ–° hg update
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
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
Interpreter Implementation Choices
Groovy indy 20120222
{{#tags}}- {{label}}
{{/tags}}