On Wed, Jul 31, 2002 at 05:51:52PM -0400, Jeff Urlwin wrote: > > > Jeff; > > It seems that you are noting the same peculiarities as I did. > > Basically; do effectively nothing in the script and watch the > > memory disappear. > > I think that's the loading of modules and if you have a lot of objects, I > believe that may contribute (but others on the list will surely correct me > where I'm wrong :) I noticed a hit when connecting the first time, but > after that, it's much stabler.
Yes, ignore everything that happends before the first connect. > > I think your test app is a better test program than I could have > > given you. > > My application is several thousand lines of code, and I doubt > > that a distilled version would be representative. > > It would be nice to know if you are loading a lot of modules...and > instantiating objects based upon them. That may be a big part of it. What > would concern me greatly is that each iteration of the loop the memory grows > and all you are doing is database access. I've had quite a few programs > written using DBI and DBD::Oracle in the past which simply loop on the > database and create/reset the password/inactivate NT user accounts based > upon database entries...and that just ran in a loop on a production machine. > No-one saw a memory leak. If there was one, it was hardly noticable...even > over weeks. Tim.
