Date: Thu, 14 Apr 2005 18:25:43 +0200 From: Holger Kipp <hk@alogis.com> To: stable@freebsd.org Subject: Strange Shared Memory values: Apache::SizeLimit on 5.3-STABLE Message-ID: <20050414162543.GA73129@intserv.int1.b.intern> In-Reply-To: <20050414100301.GA64468@intserv.int1.b.intern> References: <20050414100301.GA64468@intserv.int1.b.intern>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, I am using Apache::SizeLimit and have the folowing problem: Process exits with the correct SIZE-Limit, but the SHARE-Size I get look a bit strange. As a result of this, checking for MAX_UNSHARED seem not to work. here a few results: exiting at SIZE=60004 KB SHARE=11733744 KB REQUESTS=2058 LIFETIME=55408 exiting at SIZE=60036 KB SHARE=11688304 KB REQUESTS=2043 LIFETIME=55154 exiting at SIZE=76088 KB SHARE=1009904 KB REQUESTS=166 LIFETIME=1988 exiting at SIZE=60084 KB SHARE=9565628 KB REQUESTS=1686 LIFETIME=54152 Anyone has an idea why SHARE goes up to 11GB or more? Is this a badly written application, or could this also be BSD::Resource returning wrong values here? Unfortunately I cannot check the application itself... top gives eg the following values for memory useage: 61828 57556 (Size, Res) This is on a 2GB HP ProLiant Dual Xeon System with FreeBSD 5.3-STABLE. Any help and/or explanation welcome! Especially: how can a single process have that much shared memory with a total of 350-400MB physical memory in use. Regards, Holger Kipp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050414162543.GA73129>