Re: Re: Re: Re: Memory leak with DBD::Sybase ?

The records being processed are all approximately the same size (Sybase IMAGE type). If the memory goes back to the pool and gets reused, it doesn't explain the constant growth of memory.

Comment on Re: Re: Re: Re: Memory leak with DBD::Sybase ?

Replies are listed 'Best First'.
Re: Re: Re: Re: Re: Memory leak with DBD::Sybase ? by one4k4 (Hermit) on Jun 05, 2003 at 22:44 UTC
Does "constant growth" mean: The first time you process 200 records, the second 204, the third 100, the fourth 300? That'd tend to tell me that Perl is indeed reusing the memory and only growing when it needs to grow.. Then again, you said "constant". On a related note, how can I watch the usage of memory during the execution of a script? "top" ordered by size isn't really what I think Anonymous Monk is doing.. One4k4 - perlmonks@poorheart.com (www.poorheart.com)	[reply]
Re: Re: Re: Re: Re: Memory leak with DBD::Sybase ? by mpeppler (Vicar) on Jun 06, 2003 at 06:10 UTC
Are you processing the IMAGE columns with the ct_send_data() API, or with a normal insert? Michael	[reply]