Note that there are some explanatory texts on larger screens.

plurals
  1. POPHP 5.5 OPCache not working on apache
    primarykey
    data
    text
    <p>I'm in charge of the opcode cache exchange here in my company, we're moving from eaccelerator to the Zend OPCache shipped with PHP 5.5.</p> <p>When I access PHP in CLI, it seems like the OPCache is working fine:</p> <pre><code>PHP 5.5.5 (cli) (built: Oct 15 2013 10:29:13) Copyright (c) 1997-2013 The PHP Group Zend Engine v2.5.0, Copyright (c) 1998-2013 Zend Technologies with Zend OPcache v7.0.3-dev, Copyright (c) 1999-2013, by Zend Technologies </code></pre> <p>But when I access my website via Apache, the benchmarks show no improvements compared to the same pages using no opcode cache. Also, <code>get_loaded_extensions(true)</code> returns an empty array.</p> <p>Can anyone answer me why on earth it isn't working?</p> <p>I'm using windows 7, Apache 2.4.6 from Apache Lounge, PHP 5.5.5 from windows.php.net.</p> <hr> <p>EDIT:</p> <p>As requested, my OPCache configuration:</p> <pre><code>[opcache] opcache.enable=1 opcache.enable_cli=1 opcache.memory_consumption=128 opcache.interned_strings_buffer=8 opcache.max_accelerated_files=4000 ;opcache.max_wasted_percentage=5 ;opcache.use_cwd=1 ;opcache.validate_timestamps=1 opcache.revalidate_freq=60 ;opcache.revalidate_path=0 ;opcache.save_comments=1 ;opcache.load_comments=1 opcache.fast_shutdown=1 ;opcache.enable_file_override=0 ;opcache.optimization_level=0xffffffff ;opcache.inherited_hack=1 ;opcache.dups_fix=0 ;opcache.blacklist_filename= ;opcache.max_file_size=0 ;opcache.consistency_checks=0 ;opcache.force_restart_timeout=180 ;opcache.error_log= ;opcache.log_verbosity_level=1 ;opcache.preferred_memory_model= ;opcache.protect_memory=0 </code></pre>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload