About php memory release problem_PHP tutorial

About php memory release issue

I took a whole morning today to look at the code that solved the memory problem before. Relatively speaking, I am very dissatisfied with the optimization program of my code. Importing 40,000 pieces of data at a time makes the code so cumbersome. I I don't think this is the fundamental solution. Through online search, we can further analyze the problem:

In the problem of PHP memory overflow, the first two methods will not be mentioned (you can refer to "About PHP Memory Release Issues" in the Expo). It is not difficult to analyze. In fact, the key to the problem lies in how to synchronize in the loop. Release memory instead of looping hundreds of times to release it once, because you will find during debugging that if we encapsulate the highly reusable code in the loop into a function, and then use the form of calling a sub-function, the program will The execution speed is reduced by about dozens of times, and this decrease will change with the amount of data.

In the form of nested loops, when processing arrays with large amounts of data, many use unset($a) to release memory in time, but in fact it is meaningless to do so. Quote the following analysis:

"In the engine, variable names and their values ​​are actually two different concepts. The value itself is an unnamed zval* storage (in this case, a string value), which is passed through zend_hash_add( ) is assigned to variable $a. What happens if both variable names point to the same value?

{

zval *helloval;

MAKE_STD_ZVAL(helloval);

ZVAL_STRING(helloval, "Hello World", 1);

zend_hash_add(EG(active_symbol_table), "a", sizeof("a"), &helloval, sizeof(zval*), NULL);

zend_hash_add(EG(active_symbol_table), "b", sizeof("b"), &helloval, sizeof(zval*), NULL);

}

At this point, you can actually look at $a or $b and see that they both contain the string "Hello World". Unfortunately, next, you continue to execute the third line of code "unset($a);". At this time, unset() does not know that the data pointed to by the $a variable is also used by another variable, so it just blindly releases the memory. Any subsequent access to variable $b will be interpreted as freed memory space and thus cause the engine to crash.

This problem can be solved with the help of the fourth member refcount of zval (which has several forms). When a variable is first created and assigned a value, its refcount is initialized to 1 because it is assumed to be used only by the corresponding variable when it was originally created. When your code snippet starts assigning helloval to $b, it needs to increase the value of refcount to 2; thus, the value is now referenced by two variables:

{

zval *helloval;

MAKE_STD_ZVAL(helloval);

ZVAL_STRING(helloval, "Hello World", 1);

zend_hash_add(EG(active_symbol_table), "a", sizeof("a"), &helloval, sizeof(zval*), NULL);

ZVAL_ADDREF(helloval);

zend_hash_add(EG(active_symbol_table), "b", sizeof("b"), &helloval, sizeof(zval*), NULL);

}

Now, when unset() deletes the corresponding copy of $a from the original variable, it will be able to see from the refcount parameter that there is someone else interested in the data; therefore, it should just decrement the refcount count value and then leave it alone. "

In summary, what we need to do most is actually to reduce the array in which data is initially stored. In the above example, the processed elements in the array are released in time during the loop, so that the memory usage will continue to increase as the loop continues. Fluctuation (memory recycling mechanism problem), but not growing all the time, thus achieving our original purpose. Of course, the maximum amount of data processed at one time still depends on the memory allocated by the server to PHP. If the amount of data read into the array in a single time exceeds the limit, even the gods will not be able to do anything, haha.

http://www.bkjia.com/PHPjc/972220.htmlwww.bkjia.comtruehttp: //www.bkjia.com/PHPjc/972220.htmlTechArticleAbout the problem of php memory release I spent a whole morning today and looked at the code that solved the memory problem before. Relatively speaking, I am very dissatisfied with the optimization process of my code, once...