How cache an array of objects between pages

[FluffyCat]

Hi 

 

I have a small module that gets all the categories and puts them in an array like this:

$myCategories = Category::getHomeCategories($this->context->language->id);

 

However this is done in hookDisplayTop so every time a new page shows we have to ask the database for these categories. This just seems a bit unnecessary.

 

So I wonder if there is a way to cache, for the whole shop or for each user, this array with objects so that when I enter hookDisplayTop I could do something like:

 

if ($myCategories == NULL)

  $myCategories = Category::getHomeCategories($this->context->language->id);

 

Would this be more efficient than calling the function above for each page?

 

 

[Alex Simonchik BelVG]

Hi,

 

you can create your own hook and call it for specific situation, for example {hook h="myCustomHook"}. Also you can using cache for best performance.

 

Regards

[Fabien Serny]

You can do something like this :

$myCategories = Configuration::get('HOME_CAT_CACHE_'.$this->context->language->id);
if ($myCategories == '')
{
    $myCategories = json_encode(Category::getHomeCategories($this->context->language->id));
    Configuration::updateValue('HOME_CAT_CACHE_'.$this->context->language->id, $myCategories);
}
$myCategories = json_decode($myCategories);

At each page load there is MySQL request that load all Configuration values, so it will not add a request to use Configuration::get()

You should also add a condition to delete cache each day (that will help to refresh categories if they changed).

 

Edit : You could also cache the object in json in a cache file, but I think, in your case, store it in the Configuration::get will be okay

Edited May 2, 2014 by Fabien Serny (see edit history)

[Fabien Serny]

@Alex, I'm not sure she wanted to create a new hook, and about the cache, she was asking how

[a_simonchik]

Fabien, OK this is not so hard FluttyCat there is simple article for describe whole proccess of work with standart Prestashop Cache: http://blog.belvg.com/prestashop-cache.html

 

Regards

[Alex Simonchik BelVG]

Sorry, previous post by me, I am use the old account

 

Regards

[FluffyCat]

Thanks for the answers. I am testing with the Cache approach now but it seems that it is clearing the cache between page loads right?

 

I have this code:

public function getCachedTopcats()

    {

        $cache_id = 'topcats_array' . $this->context->language->id;

        if (!Cache::isStored($cache_id))

        {

        echo "NOT CACHED";

        $topcats = Category::getHomeCategories($this->context->language->id);

            Cache::store($cache_id, $topcats);

        } else {

        echo "WAS CACHED";

        }

        return Cache::retrieve($cache_id);

    }

 

But reloading the page or moving to another page always prints the "NOT CACHED". So it seems this cache is invalidated between pageloads. Am I understanding that correctly? That the Cache class is only for caching things while on the same page or am I missing something here.

[FluffyCat]

Now I have tested Fabiens suggestion as well and it works fine, thanks a lot for the help.

 

Can I assume that this approach with storing the main categories in the Configuration should be faster than calling Category::getMainCategories for each pageload? Or am I trying to optimize something that does not really make a big difference?

 

Thanks again

[bellini13]

storing the array object in the configuration db table should be slightly more effective then executing the sql to locate the categories and building the array object.  but i assume we are talking milliseconds here.

 

storing the data in configuration database table will persist until you delete or change it, so now you need to deal with cleaning up the 'cache' whenever category data changes.

 

As for using the Cache object, it depends what the cache system is.  Using something like APC, then the objects will persist until they are pushed out or until the TTL expires.  This means the objects should survive multiple pageloads.  File system cache should also survive.  What cache system are you using?

 

The other mechanism is to use smarty cache.  If you are retrieving categories to be used within a smarty template, then just cache the smarty template file the first time and then re-use the cached template.  This way you only need to do the following one time (query the database, create the array object, create the template output).  Once that is done then you really only need to do it again when the underlying data or template changes.

[El Patron]

I like (fast) php serialize and unserialize.

[Fabien Serny]

Now I have tested Fabiens suggestion as well and it works fine, thanks a lot for the help.

 

Can I assume that this approach with storing the main categories in the Configuration should be faster than calling Category::getMainCategories for each pageload? Or am I trying to optimize something that does not really make a big difference?

 

Thanks again

 

Yes, it will save you one DB request (that is not nothing when we're talking about product or categories .

 

As I said, all Configuration values are load with one request at each page load. So adding one value, will not make the configuration load slower.

 

 

 

But reloading the page or moving to another page always prints the "NOT CACHED". So it seems this cache is invalidated between pageloads. Am I understanding that correctly? That the Cache class is only for caching things while on the same page or am I missing something here.

 

 

Cache class will use cache system configured in your back office.

If you're using CacheFS, for example, it might be a permission problem. If the directory "cache/cachefs/" is not writable, cache will only last during the page load since PS can't write cache file.

 

The other mechanism is to use smarty cache.  If you are retrieving categories to be used within a smarty template, then just cache the smarty template file the first time and then re-use the cached template.  This way you only need to do the following one time (query the database, create the array object, create the template output).  Once that is done then you really only need to do it again when the underlying data or template changes.

 

I totally agree with bellini13, Smarty cache will be better. I did not mention it since you talked about Smarty caching since you asked for array caching

Edited May 4, 2014 by Fabien Serny (see edit history)

[FluffyCat]

Thanks for all the help,

 

Actually, in the Prestashop backoffice the cache is not enabled but it is set to use APC from Plesk so it should be caching.

 

For the Smarty cache, is this something I must enable for my module? I thought it was on by default?

[Fabien Serny]

Nope it's not enabled by default, only Smarty compilation cache is enabled.

About the Smarty Cache, check the module blockcategories, you will see how to use it

Edited May 7, 2014 by Fabien Serny (see edit history)

[bellini13]

Actually, in the Prestashop backoffice the cache is not enabled but it is set to use APC from Plesk so it should be caching.

 

If cache is not enabled in the back office, then using the Cache object would have no effect.  You have to enable cache, and then if you select APC, you need to ensure that APC is installed and configured on your server. 

 

For the Smarty cache, is this something I must enable for my module? I thought it was on by default?

Your module needs to properly use smarty templates, and more importantly needs to apply correct usage of template caching (ie.  when data changes you need to clear that cached template file so it can be re-created and cached again)

[FluffyCat]

Great, I will have a look at the block categories and the smarty cache stuff.

 

Thanks for all the help

[El Patron]

<< still prefers serialize

 

the one thing you will need to do, no matter how you approach this is to add hooks where possible that tell you to rebuild your file cache, for example if you are caching category tree, and new/changed/deleted  category, then have hook to take appropriate action.

[prestowicz]

I like (fast) php serialize and unserialize.

 

Fought you were right with serialized data about speed but http://www.shozab.com/php-serialization-vs-json-encoding-for-an-array/ json is the absolute winner isn't it?

[El Patron]

Fought you were right with serialized data about speed but http://www.shozab.com/php-serialization-vs-json-encoding-for-an-array/ json is the absolute winner isn't it?

 

thanks for sharing....