Group items tagged

MALLOC_ARENA_MAX - starting with GLIBC Version 2.10 and higher, a new feature has emerged to help address memory locations and proximity to processor cores. Prior to this feature, everything stayed within one memory pool, so the data didn't get "closer" to the cores. . However, we have discovered that when fully utilized in CentOS/RHEL 6.x, this functionality can also generate negative side effects as excessive memory utilization.

I've never met a developer who complained about code getting faster or taking up less RAM. In Ruby, memory is especially important, yet few developers know the ins-and-outs of why their memory use goes up or down as their code executes.

In the modern era, software is commonly delivered as a service: called web apps, or software-as-a-service. The twelve-factor app is a methodology for building software-as-a-service apps that: - Use declarative formats for setup automation, to minimize time and cost for new developers joining the project; - Have a clean contract with the underlying operating system, offering maximum portability between execution environments; - Are suitable for deployment on modern cloud platforms, obviating the need for servers and systems administration; - Minimize divergence between development and production, enabling continuous deployment for maximum agility; - And can scale up without significant changes to tooling, architecture, or development practices. The twelve-factor methodology can be applied to apps written in any programming language, and which use any combination of backing services (database, queue, memory cache, etc).

As of today, all support for Ruby 1.9.3 has ended. Bug and security fixes from more recent Ruby versions will no longer be backported to 1.9.3.

necakane skoro :| som zvedavy, pri ktorej verzii zakotvia nase projekty. Ruby v2.1 ma nejake problemy s GC http://stackoverflow.com/questions/27102565/memory-usage-increase-with-ruby-2-1-versus-ruby-2-0-or-1-9 a webafis uz podporuje Ruby 2.0+ ?

If you have studied computing science, then you know how to do complexity analysis. You'll know that iterating through a linked list is O(N), binary search is O(log(N)) and a hash table lookup is O(1). What if I told you that all of the above is wrong?

the translated strings are stored on the heap, where the garbage collector must scan over the objects on every run (at least in the case of Ruby MRI). For a mature process with all the translations loaded, this is almost 1 million objects! Second, each process has its own copy of the strings.

Matz is experimenting with three concepts that may or may not be included in Ruby 3.0. 1. Man-machine collaboration through a static analyzer (e.g. rubocop or ruby-lint) that uses soft typing (i.e. inferred typing) to determine if a program will crash or not. 2. Performance enhancements through JIT compilation, but preliminary implementations have shown to increase memory consumption as a side effect. 3. Concurrency improvements through better abstractions like streams and pipelines. When used, the running program would place itself inside an event loop, disable the GIL, and force objects to be immutable. Matz calls it Rube Goldberg Programming.

A list of Ruby gems that have memory leaks