This worked while running 1.0.4, but now with the upgrade to 1.1b3, the memcache was throwing fatal errors. Unfortunately, I didn't copy down the errors.

So really, my main question is, does this all look right?? I am going to install memcache on my test site and re-enable memcache to see if I can re-create what was happening. It just seems a bit off that it worked in 1.0.4, but now with beta 3 it doesn't work. I currently have memcache off and apc running just fine on my live site, so it is definitely something with my memcache settings.

I should also state that APC is installed on the web server and memcached is installed on the DB server.

Basically, all I did was comment out the apc portion and open up the memcached portion. Now I commented out memcached and opened apc and everything works fine.

So I guess at this point, I want to best utilize what I have. There are a couple of cache threads going, but no real answers to what/how to best utilize them. It looks like XF itself will use APC without having to alter anything in the config file (as a opcode cache).

So I guess my question is, with 2 servers (1 web side and 1 DB server), what is the best caching system to implement to speed everything up?

Well-known member

I have a more detailed question, which is the best way to configure XF to work with eAccelerator? If you have a dedicated server (probably VPS too) with cPanel, you can use the EasyApache feature to set up eAccelerator, so it's a supported install, which is great if all your PHP scripts run faster.

Note: cPanel has added a very basic, mostly crippled XCache installation, but I presume this will be expanded in the future.

Basically, all I did was comment out the apc portion and open up the memcached portion. Now I commented out memcached and opened apc and everything works fine.

So I guess at this point, I want to best utilize what I have. There are a couple of cache threads going, but no real answers to what/how to best utilize them. It looks like XF itself will use APC without having to alter anything in the config file (as a opcode cache).

So I guess my question is, with 2 servers (1 web side and 1 DB server), what is the best caching system to implement to speed everything up?

I just changed out the IP in that line so I didn't post the true IP address.

The one thing that I noticed is that the error is calling out memcached on localhost, when really it is running on my 2nd server. So someplace it skipped over my set IP address and is trying to connect to 127.0.0.1. So under the host line, do I have to have a IP address (xxx.xxx.xxx.xxx), or can I have a web address (internal.myserver.com)?? That might be my problem since I am calling a web address instead of the actual internal IP, so I will try and change that around and give it another shot.

After consulting with a programmer friend, we came to the conclusion that with APC in the confige file, it was overwriting the memcached cache. So the site didn't freak out. Now I can run with the APC commented out and utilize the XF use of APC for opcode, and use memcached for backend caching on the DB server.

So this is my current config file which is running just fine and I am getting data stored in both caches.