Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50560
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain prohost.org designates 209.85.161.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <8757232E56758B42B2EE4F9D2CA019C9154CB7@US-EX2.zend.net>
References: <8757232E56758B42B2EE4F9D2CA019C9154CB7@US-EX2.zend.net>
Date: Thu, 25 Nov 2010 12:51:50 -0500
Message-ID: <AANLkTi=U4wPiPNdrFWw8ZRp4PZJZAYLrLbfQD5OMbcaY@mail.gmail.com>
To: Andi Gutmans <andi@zend.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Performance of buffer based functionality (JSON, AES, serialize())
From: ilia@prohost.org (Ilia Alshanetsky)

I think there is much to gain by improving the serialization speed in
PHP. It is used everywhere from caches like memcache, to sessions or
manual data input into DB. I would say that there are very few
non-trivial apps that would not benefit from a more compact and faster
serializer.

In our specific work-use-case switching to igbinary improved the speed
of the overall page generation by 2-3%.

On Thu, Nov 25, 2010 at 12:47 PM, Andi Gutmans <andi@zend.com> wrote:
> Hi,
>
> Completely different topic :)
>
> I've been looking a bit into performance around json encoding, hashing+encryption (aes) and serialize()/unserialize(). Data that is marshaled and often transmitted over the wire.
>
> I know there have been some high-end apps that have benefited from some custom serializers, etc... (typically platform dependent).
> I wonder if people here think improvements in these areas would move the needle for the majority of mainstream apps or not.
>
> Thanks,
>
> Andi
>