Is cache_set somehow different under the Pantheon / Mercury stack?

Events happening in the community are now at Drupal community events on www.drupal.org.
__mark's picture

I built a site on my local machine, and now I rebuilding it in a Pantheon environment and for some strange reason, my custom modules that use cache_set() are not actually inserting anything into my custom cache table.

You know how cached variables usually start out with the static $cachable_info? It almost seems like no matter what, the code is just using a value that is stored statically in that variable. No matter if I use different users, or clear the cache, it just uses a value of 1 (which I am assuming is stored in $cacheable_info), instead of getting the updated value and inserting it into the cache table.

The caching all works perfectly on my local environment. But in Pantheon, even when I comment everything out except for the lines that pull the current value, and insert them into the DB (via cache_set()) nothing is inserted into the cache table (I'm using the mysql command line tool to verify).

Anyone ever seen cache_set() behave this way?

(P.S. local is Pressflow 6.19, Pantheon is Pressflow 6.20)

Comments

After using dsm() on the

__mark's picture

After using dsm() on the result from cache_get() it shows the values as if they were pulled from the cache table, but the table still shows up as being empty using the mysql command line tool, and also in a dump of the table.

So, my only guess here is that this is actually some performance feature of Mercury that I don't understand / know about, since it seems like it's storing the values in memory and not actually hitting the database to store them?

I still have the same problem

mrded's picture

I still have the same problem on Pressflow 7.26

Mercury

Group organizers

Group categories

Post Type

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: