Hi, Jan, Our intention was to make ibis::fileManager::clear safe to call even when there are other operations on open files, however, we might not have achieved this yet. We will look into this issue in the next few days and report back to you.
John > As far as I understand, all tables opened are memory mapped and > registered in ibis::fileManager. It seems to me that deleting > tables and partitions via operator delete does not immediately > decrease the memory usage. I think they are still registered by > the fileManager instance and will still allocate memory. The > intention is probably to reuse the tables in other queries etc. A > call to ibis::fileManager::clear() in addition to calling delete > does seem to free all the memory. > > I have now few questions on this: > > - Is it safe to call ibis::fileManager::clear() even if there are > still any open tables? Does the call to clear free all objects or > just objects not opened/referenced anymore? > > - Is calling fileManager::clear() after operator delete the > intended way to decrease memory usage or are there any better > mechanisms? > _______________________________________________ FastBit-users mailing list [email protected] https://hpcrdm.lbl.gov/cgi-bin/mailman/listinfo/fastbit-users
