diff --git a/reference/wincache/ini.xml b/reference/wincache/ini.xml
index d548251594..59a919b4b7 100644
--- a/reference/wincache/ini.xml
+++ b/reference/wincache/ini.xml
@@ -41,8 +41,8 @@
wincache.fcachesize"24"
- "8"
- "128"
+ "5"
+ "85"PHP_INI_SYSTEMAvailable since WinCache 1.0.0
@@ -73,8 +73,8 @@
wincache.ocachesize"96"
- "16"
- "256"
+ "15"
+ "255"PHP_INI_SYSTEMAvailable since WinCache 1.0.0
@@ -223,7 +223,9 @@
Defines the maximum memory size (in megabytes) that is allocated for the
opcode cache. If the cached opcode size exceeds the specified value,
- then most stale opcode will be removed from the cache.
+ then most stale opcode will be removed from the cache. Note that the opcode
+ cache size must be at least 3 times bigger than file cache size.
+ If that is not the case the opcode cache size will be automatically increased.
diff --git a/reference/wincache/setup.xml b/reference/wincache/setup.xml
index 7f62ca43ca..da567fd633 100644
--- a/reference/wincache/setup.xml
+++ b/reference/wincache/setup.xml
@@ -120,6 +120,69 @@
&reference.wincache.ini;
+
+ WinCache Statistics Script
+
+ The installation package for WinCache includes a PHP script,
+ wincache.php, that can be used to obtain cache information
+ and statistics.
+
+
+ If the WinCache extension was installed via the Microsoft Web Platform Installer,
+ then this script is located in
+ %SystemDrive%\Program Files\IIS\Windows Cache for PHP\.
+ On a 64-bit version of the Windows Server operating system, the script is located in
+ %SystemDrive%\Program Files (x86)\IIS\Windows Cache for PHP.
+ If the extension was installed manually, then the wincache.php
+ will be located in the same folder from which the content of the installation package was extracted.
+
+
+ To use wincache.php, copy it into a root folder of your Web site or
+ into any subfolder. To protect the script, open it in any text editor and follow the instructions
+ in the comments:
+
+ Authentication configuration for wincache.php
+
+
+
+
+
+
+ Always protect the wincache.php script by using either
+ the built-in authentication or the server's authentication mechanism.
+ Leaving this script unprotected may compromise the security of your
+ web application and web server.
+
+
+
+
&reftitle.resources;
&no.resource;