Look into using compression to reduce the amount of storage space required for cache data in the database. Because caching (particularly intensive caching) caches each page for each user, it can consume a lot of space, particularly if there are a large number of contacts and/or users in the system.

Comments

begun’s picture

begun commented

Have added compression of cached data functionality to module. This will hopefully prove useful for those looking to gain some of the advantages of caching but have limited server space.

Ideally the site administrator would play around with the caching and compression options in namecards module to see what works best for their particular server setup.

begun’s picture

begun commented

I have modified the admin settings form submit function to clear all cached data. Previously I had used more complex logic to delete certain cached items based on the updated admin settings values. But with the addition of data compression this become more complex, as one has to start tracking which cached data is compressed/uncompressed. This means more database tables and database calls when loading cached data, which is something I want to avoid as much as possible.

begun’s picture

begun commented
Category: feature » bug
Status: Active » Fixed

Function _namecards_delete_cached_data() not found in namcards.module. Had accidentally deleted this in the previous commit. I have now put it back in and also modified it slightly, as a significant part of the code was made redundant after removing complex logic to delete cached items (see previous comment http://drupal.org/node/1269328#comment-4947608).

I have also merged the 6.x-1.x-views_caching branch back into the 6.x-1.x branch

Status: Fixed » Closed (fixed)

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