Rainbows! Rack HTTP server user/dev discussion
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org>
To: Rainbows! list <rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org>
Subject: Re: memory usage
Date: Mon, 28 Oct 2013 00:37:55 +0000	[thread overview]
Message-ID: <20131028003755.GA6569@dcvr.yhbt.net> (raw)
In-Reply-To: <526CFA8C.7000300-VwDbj2YsoUp0ZRtCdD4y8VAUjnlXr6A1@public.gmane.org>

Alexandre Riveira <alexandre-VwDbj2YsoUp0ZRtCdD4y8VAUjnlXr6A1@public.gmane.org> wrote:
> Hello Eric,
> 
> I discovered that when you restart the server (linux 2.3.50, glibc
> 2.15) memory stopped growing indiscriminately.

Linux 2.3.50?  Huh?  Assuming that's 3.2.50.  Anyways, user-visible
memory usage is only dependent on glibc version.

> 2 questions:
> 
> 1) The POOL_SIZE XEpollThreadPool series of the number of
> connections accepted epoll so'd have one for each thread

No, pool_size for XEpollThreadPool is the number of worker threads
capable of dispatching the application.  It can hold many more clients.

> 2) I saw the gem 'mall' and she seems to adjust as you indicted by
> glibc environment variables are correct? If yes in config /
> initializers added a file.rb with the following:
> Mall.opt (Mall :: ARENA_MAX, 1)
> Mall.opt (Mall :: ARENA_TEST, 1)

Yes, mall works, too, and you can tune a running app with some of the
knobs.  However, for arena settings, I think they must be set early on
(before many threads are spawned) to be effective.  So environment
variables (set before starting Ruby) are probably the best bet, since
Ruby (MRI) spawns a background timer thread right away.
_______________________________________________
Rainbows! mailing list - rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
http://rubyforge.org/mailman/listinfo/rainbows-talk
Do not quote signatures (like this one) or top post when replying


  parent reply	other threads:[~2013-10-28  0:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-22  8:28 memory usage Alexandre Riveira
     [not found] ` <52663744.6040600-VwDbj2YsoUp0ZRtCdD4y8VAUjnlXr6A1@public.gmane.org>
2013-10-22 16:09   ` Eric Wong
     [not found]     ` <20131022160930.GA3020-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
2013-10-22 18:08       ` Alexandre Riveira
2013-10-27 11:35       ` Alexandre Riveira
     [not found]         ` <526CFA8C.7000300-VwDbj2YsoUp0ZRtCdD4y8VAUjnlXr6A1@public.gmane.org>
2013-10-28  0:37           ` Eric Wong [this message]
     [not found]             ` <20131028003755.GA6569-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
2013-10-28 18:40               ` Alexandre Riveira

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://yhbt.net/rainbows/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131028003755.GA6569@dcvr.yhbt.net \
    --to=normalperson-rmlxzr9ms24@public.gmane.org \
    --cc=rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/rainbows.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).