サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
災害への備え
timetobleed.com
If you enjoy this article, subscribe (via RSS or e-mail) and follow me on twitter. tl;dr This blog post will show how a fix for XFree86 and linuxthreads ended up causing a major threading regression about 7 years after the fix was created. The regression was in pthread_create. Thread creation performed very slowly as the number of threads in a process increased. This bug is present on CentOS 5.3 (
If you enjoy this article, subscribe (via RSS or e-mail) and follow me on twitter. tl;dr This post is going to explain a serious design flaw of the object system used in MRI/REE/YARV. This flaw causes seemingly random segfaults and other hard to track corruption. One popular incarnation of this bug is the “rake aborted! not in gzip format.” theme song This blog post was inspired by one of my favor
technical ramblings from a wanna-be unix dinosaur
Hi there. First off, the slides are really great, even without the audio! So thanks a lot for making them available! I do think I might've found a little typo in slide 26: the last bullet says "obj->free.next" but it should be "obj->as.free.next" because you need to access the "free" field of the union called "as" (like the code in slide 15).
I'm sure the content of your presentation is great. Unfortunately you made two decisions that make it very difficult to read it. Decision #1: using this web site. Its is so overladen with Javascript it has totally bogged down in my browser (FF 3.014). using 900 MB (on a system with 512 Mb (1/2 GB) of RAM. a configuration which is equal to or larger than 85% of the PC's the world today.) Decision #
Quick notes before things get crazy OK, things might get a little crazy in this blog post so let’s clear a few things up before we get moving. I like the gritty details, and this article in particular has a lot of gritty info. To reduce the length of the article for the casual reader, I’ve put a portion of the really gritty stuff in the Epilogue below. Definitely check it out if that is your thing
Nothing is possible without lunch So Aman Gupta (tmm1) and I were eating lunch at the Oaxacan Kitchen on Tuesday and as usual, we were talking about scaling Ruby. We got into a small debate about which phase of garbage collection took the most CPU time. Aman’s claim: The mark phase, specifically the stack marking phase because of the huge stack frames created by rb_eval My claim: The sweep phase,
EDIT: For all those tuning into my blog for the first time be sure to check out the Ruby threading bugfix from an earlier post: Ruby Threading Bugfix: Small fix goes a long way In this blog post I’m releasing some patches to MRI Ruby 1.8.7p72 that add heap dumping, object reference finder, stack dumping, object allocation/deallocation tracking, and some more goodies to MRI Ruby 1.8.7p72. These are
このページを最初にブックマークしてみませんか?
『time to bleed by Joe Damato』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く