Re: [Pytables-users] H5Fmount?

[Mike R. <mik...@no...>]

>>>>> " " == Francesc Altet <fa...@ca...> writes:

[snip]

     > Mmm, right now, I think that PyTables can reclaim the space
     > freed in a file only if it is reclaimed in the same opening
     > session (this is ultimately an HDF5 limitation). So, perhaps
     > you can get a better behaviour if you remove the older run
     > *before* storing the new one.

  I am doing it all from one session.  But I will give your suggestion
a try.  It makes sense that a deletion before an add has a better
chance of reusing space.

[snip]

     > Yes, this is a valid point. We will add such a "mount
     > capability" to our TODO list. BTW, I see that you discovered by
     > yourself that running File.copyFile() is an equivalent way of
     > running h5repack ;-)

  I was not aware it was :).  But this does raise a question.  Does
copyFile() really exec a seperate h5repack process?  If so, then is it
important to either close() or flush the file before you call
copyFile().  If copyFile() does not flush first, I could see that
h5repack might not see all the changes made by the open pytables File.

Thanks,

Mike Romberg