Icon View Thread

The following is the text of the current message along with any replies.
Messages 11 to 16 of 16 total
Thread Memory Table - Memory not getting released back
Thu, Nov 19 2009 4:04 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Ahamed


I had a skim through the newsgroups but the only thing I could find was a suggestion to minimise / maximise the app which somehow forced Windows to release the memory.

I don't have V3 installed, I'm mainly using ElevateDB these days but if you can write a small app that demonstrates the problem without me having to click a button lots of times and let me have the source and a complied executable I'll have a look.

Roy Lambert [Team Elevate]
Thu, Nov 19 2009 1:48 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Ahamed,

Please do not post attachments in this newsgroup.  Use the binaries
newsgroup instead:

http://www.elevatesoft.com/newsgrp?action=viewthreads&group=13&page=1

I'm looking into this right now.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thu, Nov 19 2009 2:01 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Ahamed,

<< From the code you might have seen the straight forward method used...but
still the DROP table or DELETE records from table are not freeing memory. >>

Is the issue with the DeleteTable call or the deletion of records ?  3.30
works fine in terms of the DeleteTable method - it removes the table and
frees the memory.

Are you expecting the Delete method to actually reduce memory consumption
when records are deleted ?  If so, then that isn't how DBISAM works - to
free up the memory used by previously-deleted records, you'll have to call
the OptimizeTable method instead.  The OptimizeTable method will reorganize
the table so that it only occupies the memory used by non-deleted records.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thu, Nov 19 2009 2:07 PMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Tim

>Are you expecting the Delete method to actually reduce memory consumption
>when records are deleted ? If so, then that isn't how DBISAM works - to
>free up the memory used by previously-deleted records, you'll have to call
>the OptimizeTable method instead. The OptimizeTable method will reorganize
>the table so that it only occupies the memory used by non-deleted records.

Never occurred to me to use optimize on a menory table Smiley Does it then release the memory back to the heap, and what about DROP TABLE?

Roy Lambert
Fri, Nov 20 2009 2:38 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Roy,

<< Never occurred to me to use optimize on a menory table Smiley Does it then
release the memory back to the heap, and what about DROP TABLE? >>

Yes, and yes, DROP TABLE will do the same.

--
Tim Young
Elevate Software
www.elevatesoft.com

Sat, Nov 21 2009 7:23 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Tim


Thought so, at least about DROP TABLE so its probably a Windows / Citrix issue.

Roy Lambert
« Previous PagePage 2 of 2
Jump to Page:  1 2
Image