Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:50571 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 47448 invoked from network); 25 Nov 2010 19:12:55 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Nov 2010 19:12:55 -0000 Authentication-Results: pb1.pair.com smtp.mail=Michel.Bartz@manwin.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=Michel.Bartz@manwin.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain manwin.com from 206.162.131.147 cause and error) X-PHP-List-Original-Sender: Michel.Bartz@manwin.com X-Host-Fingerprint: 206.162.131.147 mail.mansef.com Received: from [206.162.131.147] ([206.162.131.147:16948] helo=mail.manwin.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 20/9C-16484-635BEEC4 for ; Thu, 25 Nov 2010 14:12:55 -0500 Received: from MANSEF-EX1.mansef.local ([10.73.1.205]) by MANSEF-EX1.mansef.local ([10.73.1.205]) with mapi; Thu, 25 Nov 2010 14:12:52 -0500 To: 'Andi Gutmans' , "'internals@lists.php.net'" Date: Thu, 25 Nov 2010 14:12:50 -0500 Thread-Topic: Performance of buffer based functionality (JSON, AES, serialize()) Thread-Index: AcuMyKPxquXeaFi0QPSLqa5adhX35wACsU6g Message-ID: <3CBAD28B2C54DF4DAFDE711618D9B99202ED4D6C29@MANSEF-EX1.mansef.local> References: <8757232E56758B42B2EE4F9D2CA019C9154CB7@US-EX2.zend.net> In-Reply-To: <8757232E56758B42B2EE4F9D2CA019C9154CB7@US-EX2.zend.net> Accept-Language: en-US, en-CA Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-CA Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: RE: Performance of buffer based functionality (JSON, AES, serialize()) From: Michel.Bartz@manwin.com (Michel Bartz) Hi, I think it would, a lot of sites/apps nowadays rely a lot on JSON encoding/= decoding, plus a lot of technologies are relying on serialization/json enco= ding (Memcached, Redis, to name a few) at the PHP level, which can be a rea= lly big performance eater if you use it a lot. On the other hand, it's not too difficult to get IGBinary setup as serializ= er instead of the default one, and it does some pretty good improvement. Ever considered making it a part of PHP? What would be the implication (as = I'm not too familiar with all the internals of PHP besides extensions...)? Michel Bartz Lead Developer Manwin Canada Skype: michel.php -----Original Message----- From: Andi Gutmans [mailto:andi@zend.com] Sent: Thursday, November 25, 2010 12:47 PM To: internals@lists.php.net Subject: [PHP-DEV] Performance of buffer based functionality (JSON, AES, se= rialize()) Hi, Completely different topic :) I've been looking a bit into performance around json encoding, hashing+encr= yption (aes) and serialize()/unserialize(). Data that is marshaled and ofte= n transmitted over the wire. I know there have been some high-end apps that have benefited from some cus= tom serializers, etc... (typically platform dependent). I wonder if people here think improvements in these areas would move the ne= edle for the majority of mainstream apps or not. Thanks, Andi This e-mail may be privileged and/or confidential, and the sender does not = waive any related rights and obligations. Any distribution, use or copying = of this e-mail or the information it contains by other than an intended rec= ipient is unauthorized. If you received this e-mail in error, please advise= me (by return e-mail or otherwise) immediately. Ce courrier ?lectronique est confidentiel et prot?g?. L'exp?diteur ne renon= ce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utili= sation ou copie de ce message ou des renseignements qu'il contient par une = personne autre que le (les) destinataire(s) d?sign?(s) est interdite. Si vo= us recevez ce courrier ?lectronique par erreur, veuillez m'en aviser imm?di= atement, par retour de courrier ?lectronique ou par un autre moyen.