[#86787] [Ruby trunk Feature#14723] [WIP] sleepy GC — ko1@...

Issue #14723 has been updated by ko1 (Koichi Sasada).

13 messages 2018/05/01
[#86790] Re: [Ruby trunk Feature#14723] [WIP] sleepy GC — Eric Wong <normalperson@...> 2018/05/01

ko1@atdot.net wrote:

[#87095] [Ruby trunk Feature#14767] [PATCH] gc.c: use monotonic counters for objspace_malloc_increase — ko1@...

Issue #14767 has been updated by ko1 (Koichi Sasada).

9 messages 2018/05/17

[ruby-core:87216] Re: [Ruby trunk Feature#14718] Use jemalloc by default?

From: Vladimir Makarov <vmakarov@...>
Date: 2018-05-22 01:12:03 UTC
List: ruby-core #87216

On 05/18/2018 10:55 PM, dennisb55@hotmail.com wrote:
> Issue #14718 has been updated by bluz71 (Dennis B).
>
>
>
> Red Hat's prime focus will be their paying customers, which is the big end of town (quite rightly). Hence glibc changes tend to favour big-iron rather than Heroku-sized instances.
>
   I doubt that this accurately reflects the reality.  Cloud is becoming 
very important to Red Hat. OpenShift, for example, contains a lot of 
Ruby code (e.g. Fluentd) which needs to work with very small memory 
footprint.  If you check openshift issues, you can find ones aimed to 
decrease memory footprint for Ruby code.

Disclaimer: it is just my personal opinion which hardly depends on the 
fact that I am a Red Hat employee.


Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

In This Thread