Re: Re: [metabase-dev] numRows in the oracle driver

Hello, On 03/11/2003 03:27 PM, George Schlossnagle wrote:

Since allocated memory is not really freed until the process ends, the memory footprint remains high for large result sets.

Ok I understand.

This memory (that which is alloc'd, free'd, but which the OS does not actively reclaim from the process) just gets paged out under memory pressure. This really isn't a concern. It get's reused as the process requires additional memory, it's simply not reclaimed by the OS. This is quite different than alloc'ing and then not free'ing it.

Yes but the problme is for instance with mysql_query() function that internally buffers the query results. If after that you copy the whole result set data to an PHP array variable it will take much memory than it is need because before you call mysql_free_result() the buffered result set is occuping a reasonable ammount of memory. Using buffered result sets may cause PHP to exceed its own memory limit, depending on the site of the result set, even before you get to the point of freeing that result set. -- Regards, Manuel Lemos