Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:74207 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 62533 invoked from network); 14 May 2014 18:35:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 May 2014 18:35:21 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.91 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.91 smtp91.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.91] ([108.166.43.91:54675] helo=smtp91.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1D/9F-15285-867B3735 for ; Wed, 14 May 2014 14:35:21 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp4.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id C5707140C63; Wed, 14 May 2014 14:35:17 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp4.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 5E7FD1412FE; Wed, 14 May 2014 14:35:17 -0400 (EDT) Message-ID: <5373B764.9060804@sugarcrm.com> Date: Wed, 14 May 2014 11:35:16 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Dmitry Stogov , Andrea Faulds CC: PHP Internals References: <6CA660EA-2858-4566-9696-D68BACFD8E58@ajf.me> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [VOTE] [RFC] 64 bit platform improvements for string length and integer From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > phpng optimizes core data structures and primitives especially to reduce > memory consumption and transfer. > The effect of the patch on phpng might be worse than on master, because it > does opposite things. Maybe we could optimize it by using different lengths for data and for language-based strings? One can plausibly argue you can have 2G string in zval, but having 2G class name is clearly out of the bounds of reality. In fact, for class names even single byte would probably be enough, but short should cover it with ample space. I understand that may mean some complications in the code, so not sure if it's really a good approach, just wanted to put it on the table to consider. If we have places that need big strings and places that need short strings, maybe we could have two types? Just an idea, not sure if it's not stupid :) -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227