Ruby 2.0 Garbage Collection
There’s been a lot of talk about the improvements in Ruby 2.0’s Garbage Collection performance. That’s a great thing, because GC in older versions of Ruby wasn’t very performant. Most of the conversation about generational GC (or other strategies) revolves around making Ruby GC more efficient. This has a great impact on your users, because less GC time means that their pages return faster. But wha
Hey Judy, don't make it bad
AI & MLLearn about artificial intelligence and machine learning across the GitHub ecosystem and the wider industry. Generative AILearn how to build with generative AI. GitHub CopilotChange how you work with GitHub Copilot. LLMsEverything developers need to know about LLMs. Machine learningMachine learning tips, tricks, and best practices. How AI code generation worksExplore the capabilities and be
Dynamic Method Definitions | Tenderlove Making
TL;DR: depending on your app, using define_method is faster on boot, consumes less memory, and probably doesn’t significantly impact performance. Throughout the Rails code base, I typically see dynamic methods defined using class_eval. What I mean by “dynamic methods†is methods with names or bodies that are calculated at runtime, then defined. For example, something like this: class Foo class_eva
The Cost of Ruby 1.9.3's GC::Profiler | James Golick
This is a long one, and y'all are busy I'm sure so here's the tl;dr: If you run ruby in production, you need to keep track of GC stats. Ruby 1.9.3's GC::Profiler does a bunch of really weird shit. It keeps a 104 byte sample of every GC run since it was enabled forever. Calling GC::Profiler.total_time loops over every sample in memory to calculate the total. The space used to keep those samples in
徹底解剖「G1GCã€å®Ÿè£…編（β版）
本書ã¯OpenJDK7ã®G1GCã®å®Ÿè£…ã¨ã€ãã‚Œã«é–¢é€£ã™ã‚‹æŠ€è¡“を解説ã—ã¾ã™ã€‚ 目次 スãƒãƒ³ã‚µãƒ¼ã®ã¿ãªã•ã¾ ã¯ã˜ã‚ã« 1.準備 2.オブジェクト管ç†æ©Ÿèƒ½ 3.ã‚¢ãƒã‚±ãƒ¼ã‚¿ 4.ãƒ’ãƒ¼ãƒ—æ§‹é€ 5.ã‚ªãƒ–ã‚¸ã‚§ã‚¯ãƒˆæ§‹é€ 6.HotspotVMã®ã‚¹ãƒ¬ãƒƒãƒ‰ç®¡ç† 7.スレッドã®æŽ’他制御 8.GCスレッド（並列編） 9.GCスレッド（並行編） 10.並行マーã‚ング 11.é€€é¿ 12.予測ã¨ã‚¹ã‚±ã‚¸ãƒ¥ãƒ¼ãƒªãƒ³ã‚° 13.æ£ç¢ºãªGCã¸ã®é“ 14.ライトãƒãƒªã‚¢ã®ã‚³ã‚¹ãƒˆ ã•ã‚‰ã«å‹‰å¼·ã—ãŸã„人㸠ãã®ä»–å‚考文献 以下ã‹ã‚‰ï¼ˆã‚る時点ã§ï¼‰æœ€æ–°ã®ebookをダウンãƒãƒ¼ãƒ‰ã§ãã¾ã™ã€‚ 徹底解剖「G1GCã€å®Ÿè£…ç·¨-20120915.epub 徹底解剖「G1GCã€å®Ÿè£…ç·¨-20120914.mobi 徹底解剖「G1GCã€å®Ÿè£…ç·¨-20120914.pdf è¬è¾ž 本書ã¯ã‚¹ãƒãƒ³ã‚µãƒ¼ã®ã¿ãªã•ã¾ã®é‡‘éŠçš„支æ´ã«ã‚ˆã£ã¦åŸ·ç†ã•ã‚Œã¾ã—ãŸã€‚ スãƒãƒ³ã‚µãƒ¼ã®ã¿ãªã•ã¾ ã‚
Python ã® GC ã®ãƒ‡ãƒãƒƒã‚°æ©Ÿèƒ½ - methaneã®ãƒ–ãƒã‚°
Python ã®ãƒ‡ãƒ¼ãƒ¢ãƒ³åž‹ã®ãƒ—ãƒã‚°ãƒ©ãƒ （具体的ã«è¨€ã†ã¨ Loggerhead ã¨ã„ㆠbzr ã®ãƒªãƒã‚¸ãƒˆãƒªãƒ–ラウザ）ãŒå¤§é‡ï¼ˆå…·ä½“çš„ã«è¨€ã†ã¨100MB以上）メモリを食ã£ã¦ã„ãŸã®ã§ã€ãれを調ã¹ãŸæ™‚ã®ãƒ¡ãƒ¢ã€‚ ã¾ãšã€æœ¬å½“ã«ãã‚Œã ã‘ã®ãƒ¡ãƒ¢ãƒªã‚’利用ã—ã¦ã„ã‚‹ã®ã‹ã©ã†ã‹ã‚’ meliae ã¨ã„ã†ãƒ¡ãƒ¢ãƒªãƒ—ãƒãƒ•ã‚¡ã‚¤ãƒ©ã§èª¿ã¹ãŸã‚“ã ã‘ã©ã€18MBãらã„ã—ã‹ä½¿ã£ã¦ãªã‹ã£ãŸã€‚ meliae ã®ä½¿ã„æ–¹ã¯ã¾ãŸä»Šåº¦ã«å›žã™ã¨ã—ã¦ã€ä»Šå›žã¯ãã‚“ãªã«ãƒ¡ãƒ¢ãƒªã‚’使ã†ã¯ãšãŒãªã„ã®ã«ãƒ¡ãƒ¢ãƒªã‚’使ã£ã¦ã—ã¾ã£ã¦ã„るケースã«ã¤ã„ã¦ã€‚ ã“ã®å ´åˆã¯ã€å¾ªç’°å‚照を大é‡ã«ä½œã‚‹ã“ã¨ã«ã‚ˆã£ã¦ãƒ¡ãƒ¢ãƒªãƒ–ãƒãƒƒã‚¯ãŒãŸãã•ã‚“確ä¿ã•ã‚Œã€å¾ªç’°å‚照コレクタãŒå®Ÿè¡Œã•ã‚ŒãŸå¾Œã‚‚（メモリブãƒãƒƒã‚¯å†…ã«1ã¤ã§ã‚‚生ã残ã£ã¦ã„るオブジェクトãŒã„ã‚‹ãªã©ã®ç†ç”±ã§ï¼‰OSã«ãƒ¡ãƒ¢ãƒªãƒ–ãƒãƒƒã‚¯ãŒè¿”ã•ã‚Œãªã„ã¨ã„ã†åŽŸå› ãŒè€ƒãˆã‚‰ã‚Œã‚‹ã€‚（循環å‚照以外ã®åŽŸå› ã§ãƒ¡ãƒ¢ãƒªãŒå¤§é‡ã«ç¢ºä¿ã•ã‚Œã¦ã‚‹å¯èƒ½æ€§ã‚‚ã‚ã‚‹ã‚“ã ã‘ã©ã） 今日ã®
1
ランã‚ング
ランã‚ング
ランã‚ング
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
{{#tags}}- {{label}}
{{/tags}}