• Hi Frederick,

    Thanks for your amazing plugin. I’ve been using WP-SuperCache and am considering switching to W3TC. Based on what I’ve read, it looks like W3TC will outperform WP SuperCache.

    After loading W3TC, I found that the W3TC seemed to work perfectly when disk caching was enabled – both normal and enhanced.

    But then I changed the cache type to APC. I also removed the conditional W3TC URL rewrite rules that was in the main .htaccess file because it seemed that these URL rewrite rules were needed for the disk cache, which stores files in the pgcache directory.

    After changing the cache type to APC, I found that the web server returned a 404 error for all the URLs. When I put the URL rewrite rules back into the .htaccess file, then W3TC worked but used the disk-based cache rather than the APC cache even though I set all cache types to be APC.

    Can you please help me figure out what is wrong?

    FYI, I verified that APC is installed on my webserver. Below is the apc-related output from phpinfo(). Please note that my shmmax value is 256MB. This should be fine because I also increased the kernel.shmmax value from the 32MB default value to 256MB.


    apc
    apc.cache_by_default => On => On
    apc.coredump_unmap => Off => Off
    apc.enable_cli => Off => Off
    apc.enabled => On => On
    apc.file_update_protection => 2 => 2
    apc.filters => no value => no value
    apc.gc_ttl => 3600 => 3600
    apc.include_once_override => Off => Off
    apc.max_file_size => 1M => 1M
    apc.mmap_file_mask => no value => no value
    apc.num_files_hint => 1000 => 1000
    apc.report_autofilter => Off => Off
    apc.rfc1867 => Off => Off
    apc.rfc1867_freq => 0 => 0
    apc.rfc1867_name => APC_UPLOAD_PROGRESS => APC_UPLOAD_PROGRESS
    apc.rfc1867_prefix => upload_ => upload_
    apc.shm_segments => 1 => 1
    apc.shm_size => 256 => 256
    apc.slam_defense => 0 => 0
    apc.stat => On => On
    apc.stat_ctime => Off => Off
    apc.ttl => 0 => 0
    apc.user_entries_hint => 4096 => 4096
    apc.user_ttl => 0 => 0
    apc.write_lock => On => On

    http://wordpress.org/extend/plugins/w3-total-cache/

Viewing 5 replies - 1 through 5 (of 5 total)
  • First of all, using APC as the page caching method is not recommended in most cases. Disk enhanced is fastest in most situations.

    Anyway, what version of APC is that? 404s using APC as the caching method is not a known issue.

    Thread Starter dparkmit

    (@dparkmit)

    Hi Frederick,

    Thanks for the guidance and the info on enhanced disk vs. APC. I assumed that enhanced disk would be faster because it would fetch the info from memory vs. disk. I’ll run our site with enhanced disk cache. Here are the versions of my software:

    • PHP: 5.2.10-2ubuntu6.3 with Suhosin-Patch 0.9.7 (cli) (built: Nov 26 2009 14:42:49)
    • Apache: Apache/2.2.12 (Ubuntu)
    • APC: 3.0.19
    • WordPress: 2.8.4
    • PHP: 5.2.10-2ubuntu6.3 with Suhosin-Patch 0.9.7 (cli) (built: Nov 26 2009 14:42:49)
    • Apache: Apache/2.2.12 (Ubuntu)
    • APC: 3.0.19
    • WordPress: 2.8.4

    I don’t see any obvious conflict with this combination. If you submit a bug submission from the support tab in the plugin, I might be able to find some other conflict.

    Thread Starter dparkmit

    (@dparkmit)

    Hi Frederick,

    I wanted to write back to let you know that I figured out the problem with my site. There were two lines at the top of my .htaccess file for the WP directory that I accidentally deleted:


    RewriteEngine On
    RewriteBase /mba

    Without these lines, Apache didn’t know how to route the request correctly because it expected the blog to not be in a sub-directory. Once I put those lines back, it worked.

    dp

    Good job!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘[Plugin: W3 Total Cache] Problem using W3TC with APC’ is closed to new replies.