As the title says, I just removed the beta version from my Drupal installation because it was flooding my syslog with messages about “trying to access field of a non-object”. I checked the project page and saw a dev version. Is the dev version ready for production use? Or are there any issues with it?

Comments

ogi’s picture

I consider filecache production ready but still some bugs pop up. Please give me samples of these errors so that this problem is fixed.

roderik’s picture

I disagree somewhat. It very much depends on your site. If it you have many cache entries (e.g. EntityCache with a large amount of nodes or other entities), you can get huge unpredictable slowdowns. I'm running a large site on production for a month now, because I had to... but it's a hastily custom-patched version, and still, I'm keeping my fingers crossed.

IMHO at least #1488870: Reorganize cache expiry behavior needs to be incorporated (which will get rid of my hasty custom patch). That will get rid of the huge unpredictable slowdowns.

See comment #1488870-1 for a list of possible things to look at, one of which might have to be done on a site where caches grow large, before huge predictable slowdowns are a thing of the past. I don't know about that yet. Hopefully I'll be able to get some test data coming in, now I'm running the production site with the module + #1211166 + #1488870.

ogi’s picture

Status: Active » Fixed

For my use cases it's production ready but I admit that in general cases it's not. Some bigger tasks started by roderik need to be completed first.

fleshgrinder’s picture

Thanks for the info ogi and the heads up roderik. I guess I wait then. :)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

smitty’s picture

Status: Closed (fixed) » Active

I Installed the module considering the readme.txt.

But I can't see any performance gains versus the build in caching mechanism. For both anonymous users and logged in users there are the same loading times of the pages.

If I disable the build in pagecache it's clearly slower for anonymous users.

In the readme.txt I found: "NOT IMPLEMENTED YET: filecache_fast_pagecache".

Does this mean, that at the moment File Cache only writes the cached files to the directory but never loads them again, meaning that only the build in caching mechanism is active for viewing the pages?

ogi’s picture

File Cache doesn't have its own page caching. What is described about unimplemented filecache_fast_pagecache is just shortcuts for tuning Drupal's own capabilities so that when cached pages are served, there's no connection to DB and this sometimes is a significant win.

ogi’s picture

Status: Active » Fixed

And about the status - it's still beta but for most of use cases it will work well.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.