While working on some old custom code I noticed that variable_set() was being used in a manner that always made new key pair values and never made a call to variable_del. These values would be read once under a certain condition and never read again.
Are persistant variables something that get cleared on clear cache or are they always building up?
if they are building up does this affect the size or speed of page load?
example:
variable_set('key_name_' . $increment, $value);
In Drupal 6 and 7, variables created with variable_set() are stored in the {variable} database table. They are not automatically cleared when the cache is cleared. They are only removed when variable_del() is called.
Whenever a page is loaded, all variables in the {variable} table are loaded into the global $conf array. So yes - if a site is automatically creating new variables at a constant rate without cleaning them up, it could in theory cause performance degradation.
You can see in the variable_get() function that it is simply loading the global $conf array and looking for the requested variable within that.
It sounds like the custom code should have been using a dedicated database table for the data it was storing, because then it would only load that information when it needed to. Variables are loaded on every pageload.
Yes.
If you find a module doing this in Drupal 7, consider checking that the value of the variable has changed before saving it, converting to use the cache system if that’s feasible, saving the value in a dedicated table if it’s not requested frequently, or like drupal_http_request() just logging the change via watchdog().
From High Performance Drupal.
