Re: [VOTE] [RFC] 64 bit platform improvements for string length and integer
| From: | Stas Malyshev | Date: | Wed, 14 May 2014 18:35:16 +0000 |
| Subject: | Re: [VOTE] [RFC] 64 bit platform improvements for string length and integer | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-74207@lists.php.net to get a copy of this message | ||
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