Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:66476
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.54 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAORXhG+U=PBACxTQJTNfR8nZWai8WYpkt=ni8OYjv29JKYWksg@mail.gmail.com>
References: <0f1001ce19ce$8ce5a260$a6b0e720$@starin.biz> <CAORXhG+U=PBACxTQJTNfR8nZWai8WYpkt=ni8OYjv29JKYWksg@mail.gmail.com>
Date: Tue, 5 Mar 2013 19:59:50 +0100
Message-ID: <CAMyk_AZT9jGkLeY-s3dZWuV5S8a6p=dQ_N+poUraQb4JatxM4g@mail.gmail.com>
To: Tom Boutell <tom@punkave.com>
Cc: nathan@starin.biz, internals@lists.php.net
Content-Type: multipart/alternative; boundary=e89a8fb1ed062dda6e04d73215bc
Subject: Re: [PHP-DEV] Memory warning hook
From: linepogl@gmail.com (Lazare Inepologlou)

--e89a8fb1ed062dda6e04d73215bc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

2013/3/5 Tom Boutell <tom@punkave.com>

> Can't you do this already? memory_limit can be fetched via ini_read,
> and together with memory_get_usage you should be able to check for
> this sort of thing. Admittedly having to parse memory_limit (which can
> be in various units) is not perfect.
>

This is not the same at all. When are you going to run this code? Memory
allocations happen all the time. What Nathan asked for is an event that is
triggered when the memory consumption reaches a threshold.

However, there is a different solution, which is better IMHO in the case of
caches: weak references. A weak reference automatically frees the memory of
the object, when the memory is needed.
http://php.net/manual/en/book.weakref.php.

Having said that, none of these solutions scale up to multiple servers.
This is why shared cache systems like memcached are recommended.




> On Tue, Mar 5, 2013 at 1:23 PM,  <nathan@starin.biz> wrote:
> > As PHP applications are turning into large frameworks one of the issues
> > arriving is memory management. One of the issues is that many framework=
s
> use
> > sophisticated caching techniques to make accessing the same data quickl=
y,
> > 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 t=
he
> > cache to be cleared out in case memory is getting low.
> >
> >
> >
> > Thoughts?
> >
> >
> >
> > Thanks,
> >
> > Software Developer
> >
> > Nathan Bruer
> >
> >
> >
>
>
>
> --
> Tom Boutell
> P'unk Avenue
> 215 755 1330
> punkave.com
> window.punkave.com
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
Lazare INEPOLOGLOU
Ing=C3=A9nieur Logiciel

--e89a8fb1ed062dda6e04d73215bc--