Skip to main content
replaced http://drupal.stackexchange.com/ with https://drupal.stackexchange.com/
Source Link

Here is the logic behind it. The cache tables stores/saves the results of your queries. So instead of having to run query X every single time, you store the results of query X in the cache table. So all you have to do is retrieve the results.

Instead of saving the cache to your database, you could/should if you can, store them in memory using modules such as Redis (maintained by BerdirBerdir) or Memcached which will retrieve the values much faster than using/querying the database.

Here is the logic behind it. The cache tables stores/saves the results of your queries. So instead of having to run query X every single time, you store the results of query X in the cache table. So all you have to do is retrieve the results.

Instead of saving the cache to your database, you could/should if you can, store them in memory using modules such as Redis (maintained by Berdir) or Memcached which will retrieve the values much faster than using/querying the database.

Here is the logic behind it. The cache tables stores/saves the results of your queries. So instead of having to run query X every single time, you store the results of query X in the cache table. So all you have to do is retrieve the results.

Instead of saving the cache to your database, you could/should if you can, store them in memory using modules such as Redis (maintained by Berdir) or Memcached which will retrieve the values much faster than using/querying the database.

added 9 characters in body
Source Link
No Sssweat
  • 31.6k
  • 14
  • 55
  • 91

Here is the logic behind it. The cache tables stores/saves the results of your queries. So instead of having to run query X every single time, you store the results of query X in the cache table. So all you have to do is retrieve the results.

Instead of saving the cache to your database, you could/should if you can, store them in memory using modules such as Memcached or Redis (maintained by Berdir) or Memcached which will retrieve the values much faster than using/querying the database.

Here is the logic behind it. The cache tables stores/saves the results of your queries. So instead of having to run query X every single time, you store the results of query X in the cache table. So all you have to do is retrieve the results.

Instead of saving the cache to your database, you could/should if you can, store them in memory using modules such as Memcached or Redis (maintained by Berdir) which will retrieve the values much faster than using/querying the database.

Here is the logic behind it. The cache tables stores/saves the results of your queries. So instead of having to run query X every single time, you store the results of query X in the cache table. So all you have to do is retrieve the results.

Instead of saving the cache to your database, you could/should if you can, store them in memory using modules such as Redis (maintained by Berdir) or Memcached which will retrieve the values much faster than using/querying the database.

added 9 characters in body
Source Link
No Sssweat
  • 31.6k
  • 14
  • 55
  • 91

Here is the logic behind it. The cache tables stores/saves the results of your queries. So instead of having to run query X every single time, you store the results of query X in the cache table. So all you have to do is retrieve the results.

Instead of saving the cache to your database, you could/should if you can, store them in memory using modules such as Memcached or Redis (maintained by Berdir) which will retrieve the values much faster than using/querying the database.

Here is the logic behind it. The cache tables stores/saves the results of your queries. So instead of having to run query X every single time, you store the results of query X in the cache table. So all you have to do is retrieve the results.

Instead of saving the cache to your database, you could/should if you can, store them in memory using modules such as Memcached or Redis which will retrieve the values much faster than using the database.

Here is the logic behind it. The cache tables stores/saves the results of your queries. So instead of having to run query X every single time, you store the results of query X in the cache table. So all you have to do is retrieve the results.

Instead of saving the cache to your database, you could/should if you can, store them in memory using modules such as Memcached or Redis (maintained by Berdir) which will retrieve the values much faster than using/querying the database.

added 271 characters in body
Source Link
No Sssweat
  • 31.6k
  • 14
  • 55
  • 91
Loading
Source Link
No Sssweat
  • 31.6k
  • 14
  • 55
  • 91
Loading