Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #19389

L

Level Up Solutions : conseil et développement d'applications web

Company blog · levups.com/en/blogprogrammingweb

Level Up Solutions : conseil et développement d'applications web is the company blog at levups.com, writing about programming and web. Since 2017, 4 different Hacker News readers have linked it 4 times, most often “Improve your Ruby application's memory usage and performance with jemalloc”. No feed was found, so read it on the site itself.

No feed foundVisit the blog
4mentions?
4HN people?
2017–2022first – last linked?
Links on Hacker News per year · peak 2 in 2018

Too few sampled comments (2) to say how often HN recommends it.?

Why HN links it

Commenters link these posts on reducing Ruby memory usage, pointing to jemalloc as a fix for MRI and large Rails apps. The links serve as examples and the comments do not judge the writing.

Summarised by Claude from a sample of 2 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

Conseil informatique et développement d'applications web depuis 1999. Solutions e-commerce depuis 2003.

Most-linked posts?

  1. Improve your Ruby application's memory usage and performance with jemalloc
    3 people · 3 mentions · first linked 2017-04-21

What Hacker News says?

  1. This is orthogonal to tenderlove's GC work, but if you're using MRI and want an easy memory usage/performance win, swap out the standard glibc malloc for jemalloc: https://www.levups.com/en/blog/2017/optimize_ruby_memory_usa...

    Comment linking /en/blog/2017/optimize_ruby_memory_usage_jemalloc_heroku_scalingo.html

    on “Reducing Memory Usage in Ruby”
  2. Submitted The difference between HTTP connect, write and read timeouts in Ruby as a story · 1 points

    HN discussion
  3. Large rails apps can see significant improvement in memory use efficiency with jemalloc e.g. as in https://www.levups.com/en/blog/2017/optimize_ruby_memory_usa... However I’ve also seen an improvement from simply setting MALLOC_ARENA_MAX=2.

    Comment linking /en/blog/2017/optimize_ruby_memory_usage_jemalloc_heroku_scalingo.html

    on “Testing Memory Allocators: ptmalloc2 vs. tcmalloc vs. hoard vs. jemalloc”
  4. Submitted Improve your Ruby application's memory usage and performance with jemalloc as a story · 1 points

    HN discussion

Search all of HN for levups.com