Re:6 Line EventMachine Bugfix = 2x faster GC, 13x requests/sec
by rcoder on Wednesday April 29, 2009 @12:10PM
(#585271)
And this, kids and kid-ettes, is why having someone who knows their way around your C compiler, assembler, and debugger on your team can be worthwhile, even if you're working in a high-level language like Ruby.
[ Parent
| on HN ]
Re:6 Line EventMachine Bugfix = 2x faster GC, 13x requests/sec
by judofyr on Wednesday April 29, 2009 @12:11PM
(#585275)
Even if you're working in a high-level language like a C extension to Ruby?
Re:6 Line EventMachine Bugfix = 2x faster GC, 13x requests/sec
by jey on Wednesday April 29, 2009 @12:58PM
(#585387)
They had to patch the C extension to make their Ruby code go faster. They weren't hacking the C extension to begin with.
Re:6 Line EventMachine Bugfix = 2x faster GC, 13x requests/sec
by scott_s on Wednesday April 29, 2009 @02:08PM
(#585550)
It certainly looks like a C++ module is part of their project: http://github.com/eventmachine/eventmachine/tree/master
Re:6 Line EventMachine Bugfix = 2x faster GC, 13x requests/sec
by alexgartrell on Wednesday April 29, 2009 @04:45PM
(#585822)
As a representative of kids and kid-ettes, that stuff is actually still taught. In addition to writing malloc and a proxy, we (I'm a TA) have labs that are designed to force students to disassemble and reverse engineer compiled code. Further, this is actually a required course for Computer Science majors and Electrical and Computer Engineers at my school.
We're keepin' it real
Re:6 Line EventMachine Bugfix = 2x faster GC, 13x requests/sec
by ice799 on Wednesday April 29, 2009 @05:27PM
(#585910)
timetobleed guy here - I'm a CMU CS alumn (class of '07). I miss the good old days of 213 and 410 =]
Re:6 Line EventMachine Bugfix = 2x faster GC, 13x requests/sec
by matt on Wednesday April 29, 2009 @07:01PM
(#586061)
Those of us who work with Joe can vouch for that :)
Re:6 Line EventMachine Bugfix = 2x faster GC, 13x requests/sec
by yan on Wednesday April 29, 2009 @01:32PM
(#585469)
I think in this case, knowing how a GC works was more important than knowing your way around the tools they used. Don't get me wrong, knowing what a compiler does, how to use gdb well, and the semantics of the stack well is important, but I think, in this scenario, understanding the garbage collection algorithm was more important than the tools they used.