Freeing memory when using Databases

code green

Does mssql_close() implictly call mssql_free_result()?

I am having memory overflow problems (temporarily set to 72mb)
when including three other scripts from one that all query a mssql database.

All three will run on their own without problem so I am looking at trying to free memory within each script.
They are all 'includes' so the garbage collector does not come into play until the main script ends.

Each scripts connects and disconnects from the DB.
Does mssql_free_result() need to be called as well?

Markus

Quote:

Originally Posted by code green

Does mssql_close() implictly call mssql_free_result()?

I am having memory overflow problems (temporarily set to 72mb)
when including three other scripts from one that all query a mssql database.

All three will run on their own without problem so I am looking at trying to free memory within each script.
They are all 'includes' so the garbage collector does not come into play until the main script ends.

Each scripts connects and disconnects from the DB.
Does mssql_free_result() need to be called as well?

You would expect it to - for the time being, you might explicitly free the results and see if it makes a difference. I'll look into the PHP core and see if it does.

code green

I have read online articles (sorry no reference) studying PHP and memory de-allocation, and in a lot of cases it does not work as expected.
unset() for example rarely frees up memory immediately and can even increase.

Whereas visual output such as echo is memory hungry.
I am going to try disabling the HTML output when running all scripts together (usually from a schedule task) but allow when run seperately

code green

Curious. I used mssql_free_result() at the end of the first script before closing the connection and now no memory overflow problem.

The query returns about 6400 records with 5 fields per record.
Two DATETIME fields, two DECIMAL and one small VARCHAR.

Markus

Quote:

Originally Posted by code green

Curious. I used mssql_free_result() at the end of the first script before closing the connection and now no memory overflow problem.

The query returns about 6400 records with 5 fields per record.
Two DATETIME fields, two DECIMAL and one small VARCHAR.

So no implicit memory freeing. Strange. I'll take this up on the PHP internals list.

Freeing memory when using Databases

re: Freeing memory when using Databases

re: Freeing memory when using Databases

re: Freeing memory when using Databases

re: Freeing memory when using Databases

Similar PHP bytes

/bytes/development

/bytes/it

/bytes/about