-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/05/2012 04:35 PM, George Niculae wrote: > On Mon, Nov 5, 2012 at 9:56 PM, Joe Micciche <jmicc...@redhat.com> > wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> Is there any code or algorithm in sipXecs which specifies the >> max amount of RAM and/or swap the sipX processes can use? >> > > I am not aware of such mechanism in sipxecs but wouldn't limiting > usage per user / group (that is sipxchange) work? I think this can > be done by using Linux's cgroups but not 100% sure
George, there are a few ways we can do this through user, group, limits config. However I suspect doing something like that might not be elegant. I should have elaborated a bit: we'd like to do this in such a way that all of the sipX processes are aware, and won't die if a limit is reached. (I suppose sipX does not throttle RAM usage.) I have no idea if anything in sipX reads available RAM at startup and computes how much it can consume - on a 4GB box and now a 24GB box, we see it consume as much RAM as it can and only hit swap under some unusual circumstances. And we've had a few OOM on both boxes. Alternatively, capping user sipXchange RAM consumption and leaving space for the OS /may/ work, I might give this a try on a test instance. Thanks. joe > > George > > >> >> We would like to ensure either x gb or y ratio for OS-level >> processes. For example, on our server, we have 24GB RAM: we would >> like to reserve 4GB for system, and let sipX processes consume >> the other 20GB; or specify sipX processes can use only 85% of >> RAM. >> > - -- ================================================================== Joe Micciche jmicc...@redhat.com Red Hat, Inc. http://www.redhat.com Senior Communications Engineer X (81) 44554 +1.919.754.4554 Key: 65F90FE1 ================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlCYOIkACgkQJHjEUGX5D+GSvgCgj/qVDVBlpk7op6QzNaKSUTiB l+cAoLq44CcxNzMfr4Fi7uCuC3MWFL0n =wuXV -----END PGP SIGNATURE----- _______________________________________________ sipx-dev mailing list sipx-dev@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-dev/
