Hi Dmitry, > -----Original Message----- > From: Dmitry Stogov <dmi...@zend.com> > Sent: Wednesday, February 13, 2019 12:26 AM > To: Joe Watkins <krak...@gmail.com>; Bob Weinand <bwo...@php.net>; > Nikita Popov <ni...@php.net>; Anatol Belski (a...@php.net) <a...@php.net>; > z...@php.net > Cc: PHP internals <internals@lists.php.net> > Subject: ZTS improvement idea > > Hi, > > > > > After JIT+ZTS related discussion with Joe and Bob, and some related > analyzes. > > I came to more or less formed design idea and described it at > https://wiki.php.net/zts-improvement > I thought about it as well. The reason for the additional dereference levels is probably ,that every globals structure has its own size. That way, it needs to go on the heap. What we indeed could do were handling some specific known structures a different way. It'd be like EG and others, that belong to the very core and are always available. Other globals, especially from extensions that can be built shared, would be probably still handled the old way. Maybe it would be a good start to speedup the very core as first. I'd wonder which particular data structures and mechanism you had in mind.
> This is not an RFC and I'm not sure, if I like to implement TSRM changes > myself now. > Certainly not an RFC. I'm short of time as well, perhaps it will change in a couple of months. Thanks Anatol -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
