Improvement Idea: /var/cache/mage--X

[apiuser]

Feature request from gstaniforthsessiondigital, posted on GitHub Oct 10, 2014

Instead of storing cache in a serialised array it would be much faster to store it as a native php file and var_export() the array.

If the file is .php it will get picked up via the opcache and be stored in memory but also precompiled and stored in opcache. This would also remove unserialised logic also.

[apiuser]

Comment from verklov, posted on GitHub Nov 08, 2014

@gstaniforthsessiondigital, thank you for your suggestion! Our architects will review it and we will then let you know of the investigation results.

[apiuser]

Comment from aohorodnyk, posted on GitHub Nov 10, 2014

Hello,

For improvement some users can disable check for updated scripts (php files) in opcache for performance improvement. Magento does not know about opcache engines on server. Magento need support all opcache applications (xcache, php opcache, apc and etc.) or use scripts for serializations deserializations

Thanks

[apiuser]

Comment from vpelipenko, posted on GitHub Jan 29, 2015

Internal ticket: MAGETWO-30482

[apiuser]

Comment from vpelipenko, posted on GitHub Mar 25, 2015

@gstaniforthsessiondigital, did you have a chance to look at last comment here posted by @aohorodnyk?

[apiuser]

Comment from orlangur, posted on GitHub Mar 25, 2015

@aohorodnyk,

For improvement some users can disable check for updated scripts (php files) in opcache for performance improvement. Magento does not know about opcache engines on server. Magento need support all opcache applications (xcache, php opcache, apc and etc.) or use scripts for serializations deserializations

"support all opcache applications" is not relevant for PHP 5.5+. Also, if check for updated PHP files is not disabled on production - it's simply a server misconfiguration which must be fixed.

[et_rolmos]

Bump for another review of this feature request (unless I misunderstood why this isn't being pursued).