GraalVMNative executables use only a fraction of memory and CPU resources required by a JVM, which improves utilization and reduces costs.
Cookpad 17 day Tech internship 2017 言語処ç†ç³»å…¥é–€ Rubyをコンパイルã—よã†
Ruby ã®ã‚³ãƒ³ãƒ‘イラ開発を通ã˜ã¦è¨€èªžå‡¦ç†ç³»ã‚’作ã£ã¦ã¿ã‚ˆã†ã€‚ 基礎：構文解æžçµæžœ → ãƒã‚¤ãƒˆã‚³ãƒ¼ãƒ‰ã¸ã®å¤‰æ› 発展：ã•ã‚‰ãªã‚‹æœ€é©åŒ–・高速化
CRubyå‘ã‘ã®LLVMベースã®JITコンパイラを書ã„ã¦ã„る話 - k0kubun's blog
LLRBã¨ã„ã†Rubyå‘ã‘ã®ãƒ¡ã‚½ãƒƒãƒ‰JITコンパイラを書ã„ã¦ã„ã‚‹ github.com RubyKaigi 2015ã®æœ€å¾Œã®ã‚ーノートã§@evanphxãŒã€ŒLLVMã§CRubyã®ã‚³ãƒ¼ãƒ‰ã‚’インライン化ã™ã‚‹ãƒ¡ã‚½ãƒƒãƒ‰JITを実装ã—ãŸã‚‰é€Ÿã„ã‚“ã˜ã‚ƒãã€ã¿ãŸã„ãªç™ºè¡¨ã‚’ã—ã¦ã„ãŸã®ã‚’覚ãˆã¦ã„ã‚‹ã ã‚ã†ã‹ã€‚ LLRBã¨ã„ã†ã®ã¯ã¾ã•ã«ãれを実装ã—ã¦ã„るプãƒã‚¸ã‚§ã‚¯ãƒˆã§ã‚ã‚Šã€å°‘ãªãã¨ã‚‚ç¾æ™‚点ã§ã€ŒLLVMã§CRubyã®ã‚³ãƒ¼ãƒ‰ã‚’インライン化ã™ã‚‹ãƒ¡ã‚½ãƒƒãƒ‰JITã€ã¨è¨€ãˆã‚‹çŠ¶æ…‹ã¾ã§å®Ÿè£…ã§ãã€ã‚‚ã®ã«ã‚ˆã£ã¦ã¯åŠ¹æžœãŒå‡ºã‚‹çŠ¶æ…‹ã«ãªã£ãŸã®ã§å…¬é–‹ã—ãŸã€‚ ãªã‚“ã§æ›¸ã„ã¦ã‚‹ã® 言語を自分ã§å®Ÿè£…ã™ã‚‹ã¨ãã®è¨€èªžã«é–¢ã™ã‚‹ç†è§£ãŒå¤§åˆ†æ·±ã¾ã‚‹ã€ã¨ã„ã†ã®ã‚’Hamlã®å®Ÿè£…ã¨ã‹Cコンパイラã¨ã‹ã§ä½“験ã—ã¦ã„ã¦ã€åƒ•ãŒä¸€ç•ªå¥½ããªè¨€èªžã¯Rubyãªã®ã§Rubyã§ã‚‚ãれをやã£ã¦ãŠããŸã„ã€ã¨ã„ã†ã®ãŒã‚ã£ãŸã€‚ã¾ãŸã€Rubyã¯é…ã„ã¨è¨€ã‚ã‚ŒãŒã¡ã ãŒã€ã©ã“ã«æ”¹å–„å¯èƒ½ãªç‚¹ãŒçœ ã£ã¦ã„ã‚‹
How to use headless Chrome to power your automated tests
≡ Google Chrome version 59 will ship with the headless option. This means you can test your web applications using chrome without needing xvfb. One problem: the latest chromedriver (version 2.29) doesn't support versions of Chrome higher than 58. The solution is to build the latest chromedriver that supports the latest chrome/chromium. Google does not make nightly builds of chromedriver public, yo
Koichi Sasada: A proposal of new concurrency model for Ruby 3 (RubyKaigi2016)
A proposal of new concurrency model for Ruby 3 Koichi Sasada ko1@heroku.com People love “Concurrency†Concurrent RubyKaigi (at least, there are two parallel sessions) Why people love (to discuss) “Concurrency� •Performance by “Parallel†execution to utilize multiple-cores •Ruby has thread system, but MRI doesn’t permit to allow parallel execution. About this presentation •Show “Why difficult mult
How to spy on a Ruby program
June 12, 2016 I love debugging tools. One of the most frustrating things to me is – when I run a Ruby or Python program, I can’t find out what that program is doing RIGHT NOW. You might eagerly interrupt me – julia, you say, you can use pdb! or pry! or rbtrace!. So, let me explain. If I’m running a program on the JVM with PID 4242, I can run jstack -p 4242, and it will print the current stack trac
binstub ã«ã¤ã„ã¦ç¿»è¨³ã—ã¦ã¿ãŸ - Qiita
https://github.com/sstephenson/rbenv/wiki/Understanding-binstubs ã®ç¿»è¨³ã§ã™ã€‚ã‹ãªã‚Šé©å½“ã§ã™ã€‚誤訳ç‰ã‚ã£ãŸã‚‰ã”指摘ã„ãŸã ã‘ã‚Œã°ã¨æ€ã„ã¾ã™ã€‚ rvm seppku ãŒã™ã”ã時間ã‹ã‹ã£ã¦æš‡ãªã®ã§ã€ãã®é–“ã« rbenv ã«ã¤ã„ã¦èª¿ã¹ã¦ãŸã‚‰ç™ºè¦‹ã—ãŸã®ã§ã—ãŸã€‚ binstub ã‚’å¦ã¼ã†ï¼ binstub ã¯å®Ÿè¡Œå¯èƒ½ãƒ•ã‚¡ã‚¤ãƒ«ï¼ˆã„ã‚ゆるãƒã‚¤ãƒŠãƒªãƒ¼ã€ã‚³ãƒ³ãƒ‘イルã•ã‚Œã¦ã„ã‚‹ã¨ã¯é™ã‚‰ãªã„）をラップã—ã¦ã„るスクリプトã§ã€ãã®ç›®çš„ã¯å…ƒã®å®Ÿè¡Œå¯èƒ½ãƒ•ã‚¡ã‚¤ãƒ«ã‚’呼ã³å‡ºã™å‰ã«ç’°å¢ƒã‚’æ•´ãˆã‚‹ã“ã¨ã§ã‚る。 Ruby ã®ä¸–ç•Œã§ã„ã†ã¨ã€RubyGems ã¯å®Ÿè¡Œå¯èƒ½ãƒ•ã‚¡ã‚¤ãƒ«ã‚’å«ã‚“ã gem をインストールã—ãŸå¾Œã«ã€ãã„ã¤ã® binstub を生æˆã—ã¦ã„ãŸã‚Šã™ã‚‹ã€‚binstub ã¯ã©ã‚“ãªè¨€èªžã§ã‚‚書ã‘ã‚‹ã‹ã‚‰ã€è‡ªåˆ†è‡ªèº«ã§æ›¸ã„ã¦ã¿ã¦ã‚‚良ã„ã‚“ã˜ã‚ƒãªã„ã‹ãªã€‚ Ruby Gems gem
Pythonista以外ãŒç’°å¢ƒã‚’汚ã•ãšã«Jupyter Notebookã«è§¦ã‚Œã‚‹æ–¹æ³• ã‚ã‚‹ã„ã¯ï¼ŒRubyist以外ãŒç’°å¢ƒã‚’汚ã•ãšã«Jupyter Notebookã§Rubyã«è§¦ã‚Œã‚‹æ–¹æ³• - Qiita
TL;DR Jupyter NotebookãŒã‚¢ãƒ„ã„ï¼ Rubyã¨ã‹Elixirã‚‚å‹•ã‹ã—ã¦ã¿ãŸã„ï¼ Dockerコンテナã§å‹•ã‹ã›ã°æ¥½ï¼ Docker Toolboxã ã‘ã§OKï¼ Pythonã®çŸ¥è˜ãªãã¦ã‚‚環境構築ã§ãã‚‹ Rubyã‚„Elixirã®çŸ¥è˜ãŒãªãã¦ã‚‚Jupyter Notebook上ã§ãれらã®è¨€èªžãŒæ‰±ãˆã‚‹ Jupyter Notebookã«ã¤ã„㦠Jupyter NotebookãŒã‚テるï¼ã¨ã„ã†è©±ã¯è‰²ã€…ãªã¨ã“ã‚ã§ãªã•ã‚Œã¦ã„ã‚‹ãŸã‚本稿ã§ã¯çœç•¥ã™ã‚‹: JupyterãŒã™ã”ã„å‹¢ã„ã§ã‚„ã£ã¦ãã‚‹ã‹ã‚‰ãŠå‰ã‚‰å‚™ãˆã¨ã‘（IPython Notebook + R） - Qiita Railsエンジニアã«å½¹ç«‹ã¤Jupyter Notebookã¨iRuby - クックパッド開発者ブãƒã‚° ç¾ä»£ã®ã‚¨ãƒ³ã‚¸ãƒ‹ã‚¢ã®ãŸã‚ã®å¼·åŠ›ãªãƒ¡ãƒ¢å¸³ Jupyter notebookã®ã™ã‚ã‚ - クックパッド開発者ブãƒã‚° ã“ã®Ju
Rubyã®ã‚·ã‚°ãƒŠãƒ«ãƒãƒ³ãƒ‰ãƒ© - tmtms ã®ãƒ¡ãƒ¢
toRuby & guRuby 出張版 ã§ã‚·ã‚°ãƒŠãƒ«ã«ã¤ã„ã¦ã‚„ã£ã¦ãŸã®ã§ã€é–¢é€£ã—ã¦æ›¸ã„ã¦ã¿ã¾ã™ã€‚ ã©ã®ã‚ˆã†ãªæ™‚ã«ã‚·ã‚°ãƒŠãƒ«ãƒãƒ³ãƒ‰ãƒ©ã‚’定義ã™ã‚‹ã®ã‹ ã©ã®ã‚ˆã†ãªæ™‚ã«ã‚·ã‚°ãƒŠãƒ«ãƒãƒ³ãƒ‰ãƒ©ã‚’定義ã™ã‚‹ã®ã‹ã¨ã„ã†è©±ãŒã‚ã‚Šã¾ã—ãŸã€‚ UNIXã®ãƒ‡ãƒ¼ãƒ¢ãƒ³ãƒ—ãƒã‚°ãƒ©ãƒ ã¯ã€ä½•ãŒç”±æ¥ãªã®ã‹ã‚ã‹ã‚Šã¾ã›ã‚“ãŒã€SIGHUP ã§è¨å®šãƒ•ã‚¡ã‚¤ãƒ«ã®å†èªã¿è¾¼ã¿ã‚’è¡Œã†ã®ãŒæ…£ç¿’ã«ãªã£ã¦ã„ã¾ã™ã€‚ SIGHUP ã¯ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå‹•ä½œã§ã¯ãƒ—ãƒã‚°ãƒ©ãƒ を終了ã•ã›ã¦ã—ã¾ã†ã ã‘ãªã®ã§ã€SIGHUP ã§ç‰¹åˆ¥ãªå‡¦ç†ã‚’è¡Œã„ãŸã„プãƒã‚°ãƒ©ãƒ ã¯ã‚·ã‚°ãƒŠãƒ«ãƒãƒ³ãƒ‰ãƒ©ã‚’定義ã—ã¦ã„ã¾ã™ã€‚ æœ¬æ¥ SIGHUP ã¯ç«¯æœ«ãŒçµ‚了ã—ãŸæ™‚ã«ç«¯æœ«ä¸Šã§å‹•ã„ã¦ã„ãŸãƒ—ãƒã‚°ãƒ©ãƒ ã«å¯¾ã—ã¦OSãŒç™ºè¡Œã™ã‚‹ãŸã‚ã®ã‚‚ã®ã§ã™ã€‚ ãŸã¨ãˆã°ã€ç«¯æœ«ã‚¨ãƒŸãƒ¥ãƒ¬ãƒ¼ã‚¿ã‚’é–‹ã„ã¦ã€ % sleep 9999 ã¨å®Ÿè¡Œã—ã¦ã‚‹çŠ¶æ…‹ã§ç«¯æœ«ã‚¨ãƒŸãƒ¥ãƒ¬ãƒ¼ã‚¿ã‚’é–‰ã˜ã‚‹ã¨ sleep プãƒã‚»ã‚¹ã« SIGHUP ãŒé€ã‚‰ã‚Œã¾ã™ã€‚別ã®ç«¯æœ«ã‹ã‚‰ strace
Forking and IPC in Ruby, Part II — SitePoint
Stay Relevant and Grow Your Career in TechPremium ResultsPublish articles on SitePointDaily curated jobsLearning PathsDiscounts to dev toolsStart Free Trial7 Day Free Trial. Cancel Anytime. Key Takeaways Forking in Ruby, though relatively expensive, can compete with threading if the Ruby implementation doesn’t squander Copy-on-Write optimization. However, data produced by a method called in a fork
Forking and IPC in Ruby, Part I — SitePoint
Stay Relevant and Grow Your Career in TechPremium ResultsPublish articles on SitePointDaily curated jobsLearning PathsDiscounts to dev toolsStart Free Trial7 Day Free Trial. Cancel Anytime. Key Takeaways The fork() system call in Ruby allows for the creation of a new process, enabling arbitrary code to run asynchronously and concurrently. This allows for thinking in terms of processes rather than
CRubyã®GVLã¨ãƒ“ジーループ - kyabã®æ—¥è¨˜
mrubyã®VMã®ãƒžãƒ«ãƒã‚¹ãƒ¬ãƒƒãƒ‰å¯¾å¿œãŒgithubã«ã¦è°è«–ã•ã‚Œã¦ã„ã¾ã™ã€‚ multi-thread support on the RiteVM #1657 自分もthread-safeãªVMãŒæ¬²ã—ã„ãªãã¨æ€ã£ã¦ã„ã¾ã™ã€‚STM32F4Discoveryã«FreeRTOS載ã›ã¦ä½¿ã£ã¦ã¿ãŸã„。 並行・並列処ç†ã®æˆ¦å›½æ™‚代? ã•ã¦ã€ãƒžãƒ«ãƒã‚³ã‚¢ãŒæ™®é€šã«ãªã£ãŸã—ã€Webアプリã®C10Kå•é¡ŒãŒã‚ã‚‹ã®ã§ä¸¦è¡Œãƒ»ä¸¦åˆ—処ç†ã¯æ˜¨ä»Šã®ãƒˆãƒ”ックã§ã™ï¼ˆå¤šåˆ†ï¼‰ã€‚ ãŸã マルãƒã‚¹ãƒ¬ãƒƒãƒ‰ãƒ—ãƒã‚°ãƒ©ãƒŸãƒ³ã‚°ã¯é›£ã—ã™ãŽï¼ã¨ã„ã†ã¯æ˜”ã‹ã‚‰è¨€ã‚ã‚Œã¦ã„ãŸã“ã¨ã§ã™ã€‚ ã§ã€ã‚‚ã†ã¡ã‚‡ã„並行・並列処ç†ã‚’書ãã‚„ã™ã出æ¥ãªã„ã®ã‹ã‚ˆï¼Ÿã¨ã„ã†ã“ã¨ã§Erlang,go,Scala(Actor),EventMachine,Thread pool ,node.js,deferred,future,java.util.concurrent色々出ã¦ãã¾ã—㟠（言語ã¨ãƒ©ã‚¤
Railsã§API開発ã™ã‚‹å‰ã«çŸ¥ã£ã¦ãŠãã¹ãï¼”ã¤ã®ã“㨠- Qiita
$ bin/rails g scaffold user name:string mail:string password:string invoke active_record create db/migrate/20151214145437_create_users.rb create app/models/user.rb invoke test_unit create test/models/user_test.rb create test/fixtures/users.yml invoke api_resource_route route resources :users, except: [:new, :edit] invoke scaffold_controller create app/controllers/users_controller.rb invoke test_un
Rhebok, High Performance Rack Handler / Rubykaigi 2015
Rhebok, High Performance Rack Handler / Rubykaigi 2015AI-enhanced description This document discusses Rhebok, a high performance Rack handler written in Ruby. Rhebok uses a prefork architecture for concurrency and achieves 1.5-2x better performance than Unicorn. It implements efficient network I/O using techniques like IO timeouts, TCP_NODELAY, and writev(). Rhebok also uses the ultra-fast PicoHTT
The OMR GC talk - Ruby Kaigi 2015
The document discusses the IBM OMR (Open Managed Runtime) toolkit, focusing on its features for improving garbage collection in Ruby, including multithreading and efficient memory allocation techniques. It highlights improvements achieved through a parallel global garbage collector and new memory allocation strategies, emphasizing compatibility with existing Ruby applications. Future work includes
Experiments in Sharing Java VM Technology with CRuby
Experiments in Sharing Java VM Technology with CRubyAI-enhanced description IBM is developing a just-in-time (JIT) compiler called Testarossa based on its Open Runtime (OMR) toolkit. The goal is to integrate the JIT compiler into MRI Ruby to improve performance without changing how MRI works. So far, the JIT supports most opcodes and can run Rails applications, but performance gains are modest. IB
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
Ruby ã§é«˜é€Ÿãªãƒ—ãƒã‚°ãƒ©ãƒ を書ã
Rubyã®Loggerã¯ã‚¹ãƒ¬ãƒƒãƒ‰ã‚»ãƒ¼ãƒ•(＆プãƒã‚»ã‚¹ã‚»ãƒ¼ãƒ•)ã‹ã©ã†ã‹èª¿ã¹ã¦ã¿ãŸ : sonots:blog
Ruby operator precedence table
Correctly Establishing Postgres Connections in Forked Environments | Heroku Dev Center
{{#tags}}- {{label}}
{{/tags}}