Hi, Teryl, The class ibis::tafel contains only in-memory data, when it is deleted, all in-memory objects associated with it will be freed. For the index building part, the data files may remain in memory after you have deleted the part object. However, they will only stay there if the memory is not needed for anything else. The file manager is to make sure the files are removed from memory when the memory is needed later.
If you spot any case where the above is not true, then you have encountered a bug. Please feel free to let us know. Thanks. John On 5/5/11 1:01 PM, Teryl Taylor wrote: > Hi John, > > Just a couple of quick questions. When I'm writing out data to disk, > I use: > > table = new ibis::tafel(); > > table->write(..); > delete table; > > Is that enough to cleanup memory? Or should I be doing something > else as well? I have a process that is writing out a lot of partition > over an extended time period and I just want to make sure I'm cleaning > up the resources properly. > > Same when I'm building indices. I do.. > > t = new ibis::part(index->output_path.c_str(), (const char*)0); > > t->buildIndexes((const char*)0, 7); > > delete t; > > is there anything else I should be doing in between partition writes? > > > Cheers, > > Teryl > > > > > > > > _______________________________________________ > FastBit-users mailing list > [email protected] > https://hpcrdm.lbl.gov/cgi-bin/mailman/listinfo/fastbit-users _______________________________________________ FastBit-users mailing list [email protected] https://hpcrdm.lbl.gov/cgi-bin/mailman/listinfo/fastbit-users
