opcode options for minify cache method

Hello,

Please check out our FAQ for assistance on installing PHP modules.

Thanks. I may be a little cloudy on the terminology. I’ve installed the OPCache module already. But from your reply and the FAQ I gather the minify settings grouped under “Dedicated/Virtual Server” refer to other modules.

Which one do you think is best to use? I saw somewhere that APC is depecrated now…

Hello,

The accelerators listed under “Dedicated/Virtual Server” are all OPCache. You just need to install the PHP module.
Alternatively, you can use Memcached or Redis

OK, that’s where I’m confused. OPCache is installed. When I do the W3T compatibility check it says “Opcodecache:installed (OPCache). Doesn’t that mean OPCache is installed?

Hello,
Sorry for the confusion, I’ve made a typo.
SO you’ve installed OpCache, which as you can see is not listed under the “Dedicated/Virtual Server”. To be able to use Opcode caching method you need to install one of the PHP modules listed under the “Dedicated/Virtual Server” and those are:
Opcode: Alternative PHP Cache (APC / APCu)
Opcode: eAccelerator
Opcode: XCache
Opcode: WinCache

Thanks for clarifying.

Which of those 4 do you recommend?

Hello,

If you are not going to use Redis or Memcached, you should go with Alternative PHP Cache (APC / APCu) as it’s most commonly used.

I notice Redis and Memcached are not among the options there. If I used something like memcached, how would I configure the minify cache method since memcached isn’t one of the options?

If you want to just point me to a good tutorial or explanation of how to set up the minify (or how to setup W3TC as a whole), feel free.

Just for kicks I tried activating minify using disk method, seemed to break the CSS.

Thanks for you help with this, by the way.

Hello,
As for other caching methods, you also need to install the PHP modules for Redis and Memcached to be available to use.
The optimal W3 Total Cache configuration takes into account a number of factors: your theme, your plugins, the technologies available on the server, etc. Since everyone’s site and traffic and theme is different, there is no one size fits all solution.
The best thing to do is to test the website on Gtmetrix and use those pieces of information to set up the plugin accordingly.
As for the Minify, if you are using Auto minify, sometimes CSS can break. It all depends on the theme files, page builder, and the plugins installed and how heavy your theme is. We are constantly updating our minify library but sometimes Auto Minify does not work as it supposed to due to the things mentioned above.
The best thing to do is to switch to Manual minify. This can get tricky and you need to spend some time with this, but when done, results are amazing.
If you go with Manual minify you can minify or combine JS files embed type using non-blocking async, non-blocking defer, etc. My advice is to try combining JS files using async.
As for the CSS, you should go with @import handling: Process
There is a wizard help button on the top of the Performance>minify page that will list you all JS and CSS files that you can add to minify. Still, you need to proceed carefully and add the files one by one and check your website frequently to see if everything is working as expected.

I installed memcached and also the php extension package, and restarted Apache.

But W3TC compatibility check reports “Memcached extension: not installed.”

I ran:

sudo yum install Memcached

and then

sudo yum install php-pecl-memcached

I’ve confirmed that memcached is running:

[ec2-user@ip-177-77-77-77 ~]$ sudo service memcached status
Redirecting to /bin/systemctl status memcached.service
● memcached.service - memcached daemon
   Loaded: loaded (/usr/lib/systemd/system/memcached.service; disabled; vendor preset: disabled)
   Active: active (running) since Mon 2019-07-08 03:00:12 UTC; 41s ago
 Main PID: 20277 (memcached)
   CGroup: /system.slice/memcached.service
           └─20277 /usr/bin/memcached -p 11211 -u memcached -m 256 -c 1024 -l 127.0.0.1,::1

What am I missing here? Why isn’t the compatibility check seeing this?

Thank you for your help

Hello,
Is Memcache available in a dropdown menu?

Yes, it is…and I just ran the compatibility check and it now shows it as installed. Seems to have been a lag there before W3TC picked it up. Problem solved!

I just changed the page cache method from “Disk Enhanced” to “Memcache.”

Thank you.

One more question:compatibility check says this:
mod_deflate: Not detected (required for disk enhanced Page Cache and Browser Cache)

But when I list my modules using sudo httpd -M, I see one in the list called “deflate_module (shared)”

I notice in httpd.conf this line:

LoadModule deflate_module modules/mod_deflate.so

So is W3TC not recognizing this because it’s called “deflate_module” here? What if I rewrote this line to read:

LoadModule mod_deflate modules/mod_deflate.so

Loaded Modules:
 core_module (static)
 so_module (static)
 http_module (static)
 access_compat_module (shared)
 alias_module (shared)
 allowmethods_module (shared)
 auth_basic_module (shared)
 auth_digest_module (shared)
 authn_core_module (shared)
 authn_dbd_module (shared)
 authn_file_module (shared)
 authn_socache_module (shared)
 authz_core_module (shared)
 authz_dbd_module (shared)
 authz_groupfile_module (shared)
 authz_host_module (shared)
 authz_user_module (shared)
 autoindex_module (shared)
 cache_module (shared)
 cache_disk_module (shared)
 cache_socache_module (shared)
 data_module (shared)
 dbd_module (shared)
 deflate_module (shared)
 dir_module (shared)
 dumpio_module (shared)
 echo_module (shared)
 expires_module (shared)
 filter_module (shared)
 headers_module (shared)
 info_module (shared)
 log_config_module (shared)
 logio_module (shared)
 macro_module (shared)
 mime_module (shared)
 remoteip_module (shared)
 reqtimeout_module (shared)
 request_module (shared)
 rewrite_module (shared)
 setenvif_module (shared)
 slotmem_plain_module (shared)
 slotmem_shm_module (shared)
 socache_dbm_module (shared)
 socache_memcache_module (shared)
 socache_shmcb_module (shared)
 status_module (shared)
 unique_id_module (shared)
 unixd_module (shared)
 vhost_alias_module (shared)
 watchdog_module (shared)
 dav_module (shared)
 dav_fs_module (shared)
 dav_lock_module (shared)
 lua_module (shared)
 mpm_event_module (shared)
 proxy_module (shared)
 lbmethod_bybusyness_module (shared)
 lbmethod_byrequests_module (shared)
 lbmethod_bytraffic_module (shared)
 lbmethod_heartbeat_module (shared)
 proxy_ajp_module (shared)
 proxy_balancer_module (shared)
 proxy_connect_module (shared)
 proxy_express_module (shared)
 proxy_fcgi_module (shared)
 proxy_fdpass_module (shared)
 proxy_ftp_module (shared)
 proxy_http_module (shared)
 proxy_hcheck_module (shared)
 proxy_scgi_module (shared)
 proxy_uwsgi_module (shared)
 proxy_wstunnel_module (shared)
 ssl_module (shared)
 systemd_module (shared)
 cgid_module (shared)
 http2_module (shared)
 proxy_http2_module (shared)

• This reply was modified 5 years, 4 months ago by Megunticook.

Quick follow-up–I found another thread in this forum with a similar question, sounds like it’s because I’m using php-fpm. I can safely assume that these modules are working fine and W3TC is using them?

Appreciate all the help here.

• This reply was modified 5 years, 4 months ago by Megunticook.
• This reply was modified 5 years, 4 months ago by Megunticook.

If you want to go ahead and mark this thread as resolved, go ahead. If I have further questions I’ll start a new thread. Kind of drifted a little from the original topic.

Hello @megunticook,

Sorry for the late reply. Glad to know that everything is working fine.
KAnd to confirm, yes, not detected means you don’t use mod_php mode, but php-fpm. We cannot detect Apache modules in that case, but that doesn’t mean it is not installed/active.
I.E. if Gzip is working, mod_deflate is installed.