Templates in memory - quick guide

[intol]

Recently, at http://www.eioba.com we were looking for a way to gain some performance. We started to use memory cache (included in eAccelerator).

So why not to keep PRADO templates and configs in memory? It's about 5-8 queries to database cache less, for every page!

Here's how to do it fast:

In your own Cache class add:

Code:

public function setRAM($key,$value,$expire)
{
eaccelerator_put($key,$value,$expire);
}

Code:

public function getRAM($key,$doUnserialize = true)
{
$value = eaccelerator_get($key);
if($value===NULL)
return false;
else
return $value;
}

and now in your default set and get mode:

Code:

protected function getValue($key)
{
if(strpos($key,"prado:")!==FALSE)
{
      return $this->getRAM($key);
}

...
(instructions for standard case)
}

Code:

protected function setValue($key,$value,$expire)
{
if(strpos($key,"prado:")!==FALSE)
{
return $this->setRAM($key,$value,$expire);
}
...
(instructions for standard case)
}

Remember to overload function generateUniqueKey to:

Code:

public function generateUniqueKey($key)
{
return $key;
}

[Kabayan]

This is nice!
This works very well with eAccelerator. Have you tried it other accelerators like APC or Memcache with this approach?

[intol]

There was no reason, so the answer is: no.

[edythor]

Hi,

intol,  could you show me, how do you keep  templates with the methods setRam y getRam?


thanks!

[intol]

If you enable caching, PRADO will automatically try to store templates in cache. Then you just need to overwrite functions "get" and "set" in your cache class:

Code:

class yourDefaultCacheClass {

function yourDefaultCacheClassGetFunction
{

if(strpos($key,"prado:")!==FALSE) //here you know, whether it's a template
{
      return $this->getRAM($key);
}

return parent::yourDefaultCacheClassGetFunction(); //for normal function execution

}
}

etc.

[iurijacob]

Man, this is very interesting! Awesome! Tanks a lot!!!

Maybe we could save the pagestate on RAM too, don´t we? I mean, overloading some methods of TPage or something. It would be very useful too.

[intol]

It's no problem. You can even use ready methods from our code above (savePageState = setCacheValue, loadPageState=getCacheValue) with some small modyfications.