因此,我有一個PHP頁面,允許用戶下載CSV文件,查看可能是一大堆記錄的內容。問題是MySQL查詢返回的結果越多,它使用的內存就越多。這並不令人感到意外,但確實存在問題。在處理MySQL查詢結果時如何限制PHP內存使用量?
我嘗試使用mysql_unbuffered_query(),但並沒有任何區別,所以我需要釋放所用什麼,我認爲是以前處理的行存儲一些其他的方式。有沒有一個標準的方法來做到這一點?
這裏有一個評論日誌說明了什麼我談論:
// Method first called
2009-10-07 17:44:33 -04:00 --- info: used 3555064 bytes of memory
// Right before the query is executed
2009-10-07 17:44:33 -04:00 --- info: used 3556224 bytes of memory
// Immediately after query execution
2009-10-07 17:44:34 -04:00 --- info: used 3557336 bytes of memory
// Now we're processing the result set
2009-10-07 17:44:34 -04:00 --- info: Downloaded 1000 rows and used 3695664 bytes of memory
2009-10-07 17:44:35 -04:00 --- info: Downloaded 2000 rows and used 3870696 bytes of memory
2009-10-07 17:44:36 -04:00 --- info: Downloaded 3000 rows and used 4055784 bytes of memory
2009-10-07 17:44:37 -04:00 --- info: Downloaded 4000 rows and used 4251232 bytes of memory
2009-10-07 17:44:38 -04:00 --- info: Downloaded 5000 rows and used 4436544 bytes of memory
2009-10-07 17:44:39 -04:00 --- info: Downloaded 6000 rows and used 4621776 bytes of memory
2009-10-07 17:44:39 -04:00 --- info: Downloaded 7000 rows and used 4817192 bytes of memory
2009-10-07 17:44:40 -04:00 --- info: Downloaded 8000 rows and used 5012568 bytes of memory
2009-10-07 17:44:41 -04:00 --- info: Downloaded 9000 rows and used 5197872 bytes of memory
2009-10-07 17:44:42 -04:00 --- info: Downloaded 10000 rows and used 5393344 bytes of memory
2009-10-07 17:44:43 -04:00 --- info: Downloaded 11000 rows and used 5588736 bytes of memory
2009-10-07 17:44:43 -04:00 --- info: Downloaded 12000 rows and used 5753560 bytes of memory
2009-10-07 17:44:44 -04:00 --- info: Downloaded 13000 rows and used 5918304 bytes of memory
2009-10-07 17:44:45 -04:00 --- info: Downloaded 14000 rows and used 6103488 bytes of memory
2009-10-07 17:44:46 -04:00 --- info: Downloaded 15000 rows and used 6268256 bytes of memory
2009-10-07 17:44:46 -04:00 --- info: Downloaded 16000 rows and used 6443152 bytes of memory
2009-10-07 17:44:47 -04:00 --- info: used 6597552 bytes of memory
// This is after unsetting the variable. Didn't make a difference because garbage
// collection had not run
2009-10-07 17:44:47 -04:00 --- info: used 6598152 bytes of memory
我希望有某種標準技術,用於處理(甚至更大)大的結果集這樣的,但我的研究沒有發現任何東西。
想法?
下面是一些代碼,通過要求:
$results = mysql_query($query);
Kohana::log('info', "used " . memory_get_usage() . " bytes of memory");
$first = TRUE;
$row_count = 0;
while ($row = mysql_fetch_assoc($results)) {
$row_count++;
$new_row = $row;
if (array_key_exists('user_id', $new_row)) {
unset($new_row['user_id']);
}
if ($first) {
$columns = array_keys($new_row);
$columns = array_map(array('columns', "title"), $columns);
echo implode(",", array_map(array('Reports_Controller', "_quotify"), $columns));
echo "\n";
$first = FALSE;
}
if (($row_count % 1000) == 0) {
Kohana::log('info', "Downloaded $row_count rows and used " . memory_get_usage() . " bytes of memory");
}
echo implode(",", array_map(array('Reports_Controller', "_quotify"), $new_row));
echo "\n";
}
只是好奇:爲什麼要使用$ NEW_ROW而不是使用$直接排? – Steve 2009-10-09 01:48:09
從我處理ORM的一些結果時,這不是一個真正的數組,我不得不將其複製到數組中,以便刪除元素。 – Rafe 2009-10-09 04:47:16