reference/mysqlnd/memory.xml
e016fe67d1f58dc26592e50a244584fcfcf2604d
e016fe67d1f58dc26592e50a244584fcfcf2604d
...
...
@@ -62,7 +62,7 @@
62
62
network buffers into the result buffer of mysqlnd. The result buffer is
63
63
made of zvals. In a second step the results are made available to the PHP script.
64
64
This final transfer from the result buffer into PHP variables impacts the memory
65
-
consumption and is mostly noticible when using buffered result sets.
65
+
consumption and is mostly noticeable when using buffered result sets.
66
66
</para>
67
67
<para>
68
68
By default the MySQL Native Driver tries to avoid holding
...
...
@@ -89,7 +89,7 @@
89
89
user variables when the result set is freed or a copy-on-write is performed.
90
90
An observer will see the total memory consumption grow until the result set
91
91
is released. Use the <link linkend="mysqlnd.stats">statistics</link> to check whether
92
-
a script does release result sets explicitly or the driver is does implicit
92
+
a script does release result sets explicitly or the driver does implicit
93
93
releases and thus memory is used for a time longer than necessary. Statistics
94
94
also help to see how many copy-on-write operations happened.
95
95
</para>
...
...
@@ -100,15 +100,11 @@
100
100
Albeit requesting copies means keeping results twice in memory, it allows
101
101
PHP to free the copy contained in <literal>$row</literal> as the result set
102
102
is being iterated and prior to releasing the result set itself. On a loaded server
103
-
optimizing peak memory usage may help improving the overall system performace
103
+
optimizing peak memory usage may help improving the overall system performance
104
104
although for an individual script the copy approach may be slower due to
105
105
additional allocations and memory copy operations.
106
106
</para>
107
107
<para>
108
-
The copy mode can be enforced by setting
109
-
<link linkend="ini.mysqlnd.fetch_data_copy">mysqlnd.fetch_data_copy</link>=1.
110
-
</para>
111
-
<para>
112
108
<emphasis role="bold">Monitoring and debugging</emphasis>
113
109
</para>
114
110
<para>
115
111