apc_sma_info
Seems to be no (easy) way at the to know how old a value fetched is and to check whether it is out of date.
I've made these wrappers so that you can fetch and store values based on a udt returned from get_last_modified_date() which should return a udt of when your data was last changed, and hence needs junking out of the cache.
<?php
function apc_fetch_udt($key){
$g = apc_fetch($key);
if ($g){
list($udt,$val) = $g;
if (get_last_modified_date()<$udt) {
$val = unserialize($val);
return $val;
} else {
apc_delete($key);
}
}
}
function apc_store_udt($key,$g){
$udt = time();
$g = serialize($g);
$apc = array($udt,$g);
apc_store($key, $apc);
}
?>
apc_store
(PECL apc >= 3.0.0)
apc_store — ذخیره یک متغیر در کاشه ذخیره داده
Description
ذخیره یک متغیر در کاشه ذخیره داده.
Note: برخلاف بسیاری از ساز و کارها در PHP، متغیرهای ذخیره شده با استفاده از apc_store() در بین درخواستها باقی خواهند ماند (تا مقدار از کاشه حذف شود).
Parameters
- key
-
ذخیره متغیر با استفاده از این نام. keyها برای کاشه منحصر بفرد هستند، پس ذخیره مقدار دوم به همراه همان key مقدار اصلی را بازنویسی خواهد کرد.
- var
-
متغیر برای ذخیرهسازی
- ttl
-
زمان باقی ماندن; ذخیره var در کاشه برای مدت ttl ثانیه. پس از گذشت ttl متغیر ذخیره شده از کاشه حذف خواهد شد (در درخواست بعدی). اگر ttl فراهم نشده باشد (یا اگر ttl برابر با 0) باشد مقدار تا زمان حذف دستی در کاشه باقی خواهد ماند و یا دیگر نمیتواند در کاشه بماند.
Return Values
Returns TRUE on success or FALSE on failure.
Examples
Example #1 یک مثال apc_store()
<?php
$bar = 'BAR';
apc_store('foo', $bar);
var_dump(apc_fetch('foo'));
?>
The above example will output:
string(3) "BAR"
See Also
- apc_add() - ذخیره یک متغیر در کاشه در محل ذخیره داده
- apc_fetch() - بازیابی یک متغیر ذخیره شده از کشاه
- apc_delete() - یک متغیر ذخیره شده از کاشه را حذف خواهد کرد
add a note
User Contributed Notes
apc_store - [13 notes]
php at tequilasolutions dot com ¶
6 years ago
TaRaKa ¶
2 years ago
Note APC version 3.1.3 there is a bug (http://pecl.php.net/bugs/bug.php?id=16814) that will display a cache slam averted warning for all writes to a cache var that exists. Slam checking can be disabled by setting apc.slam_defense = 0.
JaskaS ¶
6 years ago
if you want to store array of objects in apc use ArrayObject wrapper (PHP5).
<?php
$objs = array();
$objs[] = new TestClass();
$objs[] = new TestClass();
$objs[] = new TestClass();
//Doesn't work
apc_store('objs',$objs,60);
$tmp = apc_fetch('objs');
print_r($tmp);
//Works
apc_store('objs',new ArrayObject($objs),60);
$tmp = apc_fetch('objs');
print_r($tmp->getArrayCopy());
?>
alexey dot maksutov at gmail dot com ¶
1 day ago
APC does serialization/deserialization during store/fetch operations as well as it calls __sleep()/__wakeup(), or Serializable::serialize()/Serializable::unserialize(). Tested on PHP 5.4.1.0.
MaxTheDragon at home dot nl ¶
8 months ago
When specifying a ttl (Time-To-Live), you are allowed to use negative values. This causes a stored entry to be invalidated immediately, but note that it will not physically be removed until you read (eg. apc_fetch or apc_exists) it:
<?php
apc_store('testKey', 'testValue', -1); // ... or any negative integer.
// at this point, the key exists physically but is already technically invalidated by the ttl.
$test = apc_fetch('testKey'); // $test equals false.
// at this point, the key no longer exists physically.
?>
Although you could mimic apc_delete with a negative TTL (like when dealing with cookies), note that the difference is that apc_delete actually physically removes the entry.
This example comes in handy when you want to unit-test a class that uses APC. It's faster to use a negative TTL than a positive in combination with a sleep call to test whether the cache entry has actually been deleted. Other than that I can't think of any situations in which you could use this example, but I'm simply pointing out that doing this will not generate Exceptions or errors.
danil dot gazizov at gmail dot com ¶
1 year ago
Don't save empty arrays and empty values. Sometimes, you can get wrong apc_exists($someKey) result, that this key doesn't exists.
pere dot cil dot remove dot this at wanadoo dot fr ¶
1 year ago
Note that caching resources is not possible; even if the apc cache doesn't seems to call the serialize / unserialize functions, that doesn't means that resources can be cached!
Small non-working example:
<?php
// Setter code
$r = fopen( '/tmp/test.txt', 'r' );
var_dump( $r );
apc_store( 'test', $r );
?>
<?php
// Getter code
$d = apc_fetch( 'test' );
var_dump( $d );
echo fread( $d, 1024 );
?>
var_dump( $d ) returns Resource #n of type (Unknown). The resource is still here, but unavailable.
Dominik Deobald / Interdose ¶
2 years ago
It might be interesting to note that storing an object in the cache does not serialize the object, i.e. does not call the __sleep()/__wakeup() or serialize()/unserialize() methods.
eda-qa at disemia dot com ¶
3 years ago
Note that the TTL only takes effect when you attempt to access the variable again (at least in my version). That is, just issuing a new request to a page won't clear outdated items -- you have to call apc_fetch on that specific item.
If you call apc_info after the TTL of an item it will still be listed.
This is important if you are expecting items to be cleared to conserve memory.
sebastian at 7val dot com ¶
5 years ago
Note that since APC 3.0.15 or 3.0.16, the time-to-live-feature does not work within the same request (see http://pecl.php.net/bugs/bug.php?id=13331).
Roberto Spadim ¶
6 years ago
be sure that setting FALSE values can be wrong returned from fetch since fetch return FALSE on errors
elfi47 ¶
7 months ago
use apc_store() if you want to find out if the result of apc_delete(), apc_fetch(), apc_add(), ..... is REALLY FALSE or you have a problem with APC.
<?php
if (!apc_fetch('key')) {
if (!apc_store('apc_check', 1, -1)) {
// you have a problem with APC
}
else {
// apc works but variable isn´t set
}
}
?>
Sudhee ¶
6 years ago
It should be noted that apc_store appears to only store one level deep. So if you have an array of arrays, and you store it. When you pull it back out with apc_fetch it will only have the top level row of keys with nulls as the values of each key.
Solution to this, is to serialize the data before storing it in the cache and unserialize it while retrieving from the cache.