Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:66473
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain starin.biz from 207.198.105.69 cause and error)
Sender: "Nathan Bruer" <nathan.bruer@starin.biz>
To: <internals@lists.php.net>
Date: Tue, 5 Mar 2013 12:23:35 -0600
Message-ID: <0f1001ce19ce$8ce5a260$a6b0e720$@starin.biz>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0F11_01CE199C.424C43D0"
Thread-Index: Ac4Zzjqdr9e19GI9Qq2799tfWTnjHw==
Content-Language: en-us
Subject: Memory warning hook
From: nathan@starin.biz

------=_NextPart_000_0F11_01CE199C.424C43D0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

As PHP applications are turning into large frameworks one of the issues
arriving is memory management. One of the issues is that many frameworks use
sophisticated caching techniques to make accessing the same data quickly,
this improves speed it is at the cost of memory. Often the developer knows
these areas that cache and often times already have functions in place to
clear out the cache, however in the case where PHP is approaching or exceeds
memory limits PHP runs the GC then dies if it cannot allocate enough memory.
If we implemented "memory warning" triggers or user function that will be
called before the GC is executed which allows the user to try and free up
some memory on their own. This hopefully would give more flexibility to
allowing these advanced caching techniques but at the same time allow the
cache to be cleared out in case memory is getting low.

 

Thoughts?

 

Thanks,

Software Developer

Nathan Bruer

 


------=_NextPart_000_0F11_01CE199C.424C43D0--