Re: Re: another fix for max_input_vars.
| From: | Laruence | Date: | Thu, 05 Jan 2012 07:49:59 +0000 |
| Subject: | Re: Re: another fix for max_input_vars. | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-57227@lists.php.net to get a copy of this message | ||
Hi:
there is one way maybe is a good try.
when resize hashtable, we don't just dobule the size, instead, we
increase the hashtable size with a random delta
what do you think?
thanks
On Thu, Jan 5, 2012 at 3:33 PM, Stas Malyshev <smalyshev@sugarcrm.com> wrote:
> Hi!
>
>
>> Yes, but we still need an actual case to look at. Opcode caches
>> shouldn't be a problem unless they store some representation on disk
>> that live across server restarts. In the APC world, nobody does that. Is
>
>
> It's not that simple. Take example of FastCGI setup where processes can live
> and die independently (note that FastCGI does not mandate single-parent fork
> and in fact on Windows it doesn't work that way). In this setup opcode cache
> is shared between processes which may have different hash value, unless we
> give means to the cache to set this value on startup somehow.
>
>
> --
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
> (408)454-6900 ext. 227
--
Laruence Xinchen Hui
http://www.laruence.com/