Subject | Blob Handling consumes memory |
---|---|
Author | Florian Hector |
Post date | 2004-02-21T12:07:44Z |
Working with: IBO 4.4Aa, D7, FB 1.0.3.972, W2K
I have an application where I store documents as binary blob in the DB. Now I noticed that both
...LoadFromFile(FileName) as well as ...SaveToFile(Filename) keep consuming memory which is only
released when either the application disconnects from the DB or is closed altogether. When I read
files totaling 20 MB into the DB, memory consumption of my app. rises by 20 MB.
I prepared a simple test case to send it to Jason to have a look. To my surprise, the test
application does not consume memory. So I changed it to work against my original DB.
Here, it does consume memory again ...
Where does that leave me? Can any setting of the DB have such an effect on the client? What can I
test to further isolate the culprit?
I followed Tony Caduto's thread with a similar problem but his solution didn't help in my case.
I have tried explicid transaction handling with a hard commit after each new record, no effect...
Florian
I have an application where I store documents as binary blob in the DB. Now I noticed that both
...LoadFromFile(FileName) as well as ...SaveToFile(Filename) keep consuming memory which is only
released when either the application disconnects from the DB or is closed altogether. When I read
files totaling 20 MB into the DB, memory consumption of my app. rises by 20 MB.
I prepared a simple test case to send it to Jason to have a look. To my surprise, the test
application does not consume memory. So I changed it to work against my original DB.
Here, it does consume memory again ...
Where does that leave me? Can any setting of the DB have such an effect on the client? What can I
test to further isolate the culprit?
I followed Tony Caduto's thread with a similar problem but his solution didn't help in my case.
I have tried explicid transaction handling with a hard commit after each new record, no effect...
Florian