Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:66617
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain hotmail.com designates 65.55.111.91 as permitted sender)
Message-ID: <BLU0-SMTP195F04B804FBE9CC95227FCE2EC0@phx.gbl>
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
In-Reply-To: <CAMyk_AZ_JDE9AZGqkqTxmFKe40CB9JU1iwzhTbmPMZoZnVgR_w@mail.gmail.com>
Date: Thu, 14 Mar 2013 17:13:58 +0100
CC: PHP Developers Mailing List <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
References: <CADegSEbVU9MxX8e71tvCRLKN4SMLfcX+m=enKo13Wn=05QTEjA@mail.gmail.com> <op.wtxplogyc9evq2@nikita2206-debian> <CADegSEbK9=+OqPKqEM_-XyBk3K2cXUS_5+xiqXQnZq7foH2aaw@mail.gmail.com> <CAMyk_AZ_JDE9AZGqkqTxmFKe40CB9JU1iwzhTbmPMZoZnVgR_w@mail.gmail.com>
To: Lazare Inepologlou <linepogl@gmail.com>
Subject: Re: [PHP-DEV] feature request : easy shared memory
From: bobwei9@hotmail.com (Bob Weinand)

Am 14.3.2013 um 16:46 schrieb Lazare Inepologlou <linepogl@gmail.com>:

> Hello,
>=20
> 2013/3/14 rene7705 <rene7705@gmail.com>
>=20
>> great! :)
>>=20
>> this will do nicely. is there much overhead for storing and fetching =
these
>> variables? (ideally I would like to get a pointer)
>>=20
>>=20
> Unfortunately there is. Every object stored in APC has to be =
serialised
> first and then unserialised on retrieval. You can improve performance =
by
> using a binary serialiser (such as igBinary) instead of the default =
php one.
>=20
>=20
>=20
>=20
>>=20
>> On Thu, Mar 14, 2013 at 12:45 PM, Nikita Nefedov <inefedor@gmail.com>
>> wrote:
>>=20
>>> On Thu, 14 Mar 2013 07:05:03 -0000, rene7705 <rene7705@gmail.com> =
wrote:
>>>=20
>>> Hi.
>>>>=20
>>>> I'd like to build a replacement for SQL (yes, talk about an =
ambitious
>>>> project! ;), because the constant transferal of data in and out of =
SQL
>>>> from
>>>> Javascript (where everything might as well be object-oriented and
>>>> hierarchial) is a pain in the neck.
>>>>=20
>>>> But in order to do so, I'd very much like PHP (the server still =
controls
>>>> the data after all) to support shared memory efficiently.
>>>>=20
>>>> Something like
>>>>=20
>>>> sharedmem $bigNestedArray; // $bigNestedArray would be shared =
accross
>> the
>>>> entire server and all CPUs on it.
>>>>=20
>>>> as you now have
>>>>=20
>>>> global $bigNestedArray;
>>>>=20
>>>> would be ideal.
>>>>=20
>>>> I bet this would be useful for a host of other applications as =
well, and
>>>> fairly easy to implement.
>>>>=20
>>>> I'm an application programmer by trade, or I would hack this in =
myself.
>>>>=20
>>>> I'd much rather see the PHP development team develop this in =
properly. I
>>>> don't think it would require much time, as OS-level shared memory =
has
>> been
>>>> easy to implement since the 1990s.
>>>>=20
>>>> Please put this on the agenda, and get back to us in this thread as =
to
>>>> when
>>>> this will be available.
>>>>=20
>>>=20
>>> Hi,
>>>=20
>>> You can already do it using APC's apc_store() and apc_fetch() =
functions
>>> which let you use shared memory. But of course you should 'commit' =
every
>>> change of the fetched variable.
>>>=20
>>=20
>=20
>=20
> Lazare INEPOLOGLOU
> Ing=E9nieur Logiciel

Hi!

And there is no possibility to store the zval as raw binary data like in =
memory (deep copy?)
So that you only have to copy from ram? And replace the pointers to the =
place in the string?
This must be possible I think. And should be faster.

shmop has to be opened on every request and only supports strings.
APC, memcache,... can only save under serialized form which is slow.

Why not integrate some native shared memory mechanism which is faster =
than the extensions
which always serialize? (or as a new extension=85 but I really like the =
proposal to do like
"shared $var;" which is (nearly) impossible as an extension)

Bob Weinand=