News for hackers. Stuff that matters.
Re:TuneMyGC: Optimal MRI Ruby 2.1+ Garbage Collection by michaelmior on Thursday March 05, 2015 @10:21PM (#9155410)
It would be nice to have some idea of how these optimized settings are determined. It's also not clear to me if this is intended to work for any Ruby code, or just rails apps. In any case, this seems pretty cool as I think many (myself included) don't bother to even try to tune GC.

EDIT: I'd also like to see a privacy policy that talks about what data they collect and how it's used.

Re:TuneMyGC: Optimal MRI Ruby 2.1+ Garbage Collection by pencilcheck on Thursday March 05, 2015 @11:47PM (#9155637)
Looks like what they are collecting is in this array:

[TuneMyGc.walltime, TuneMyGc.peak_rss, TuneMyGc.current_rss, stage, GC.stat.values_at(*stat_keys), GC.latest_gc_info, meta]

In this file: https://github.com/bear-metal/tunemygc/blob/70a02b9dd252c6f5...

Or in their protocol.md: https://github.com/bear-metal/tunemygc/blob/master/doc/proto...

Re:TuneMyGC: Optimal MRI Ruby 2.1+ Garbage Collection by methodmissing on Friday March 06, 2015 @07:15AM (#9156667)
Yes, what we wanted to communicate was that nothing proprietary to your app or code gets sent on the wire. Just a few numbers about memory usage and heap status the tuner analyses.
Re:TuneMyGC: Optimal MRI Ruby 2.1+ Garbage Collection by methodmissing on Friday March 06, 2015 @07:12AM (#9156661)
Hi Michael, it originally started with a focus on Rails only, but at the moment we also support test frameworks, pure Ruby (requires some minor work on the user end), ActiveJob and Sinatra soon. We'll rework the docs and landing page to reflect this. Thanks for your feedback.