Skip to main content

Each access of a Pandas hdf5 store node is a re-copy from the file

This is obvious, but it is important to remember. 
import pandas as pd, pylab, cProfile

def create_file():
  r = pylab.randn(10000,1000)
  p = pd.DataFrame(r)

  with pd.get_store('test.h5','w') as store:
    store['data'] = p

def analyze(p):
  return [(p[c] > 0).size for c in [0,1,2,3,4,5,6,7,8,9]]


def copy1():
  print 'Working on copy of data'
  with pd.get_store('test.h5','r') as store:
    p = store['data']
    idx = analyze(p)
    print idx

def copy2():
  print 'Working on copy of data'
  with pd.get_store('test.h5','r') as store:
    idx = analyze(store['data'])
    print idx

def ref():
  print 'Working on hdf5 store reference'
  with pd.get_store('test.h5','r') as store:
    idx = [(store['data'][c] > 0).size for c in [0,1,2,3,4,5,6,7,8,9]]
    print idx

#create_file()
cProfile.run('copy1()')
cProfile.run('copy1()')
cProfile.run('copy2()')
cProfile.run('ref()')
When run with python test.py | grep "function calls" gives us 
         5340 function calls (5256 primitive calls) in 0.094 seconds
         2080 function calls (2040 primitive calls) in 0.048 seconds
         2080 function calls (2040 primitive calls) in 0.050 seconds
         5661 function calls (5621 primitive calls) in 0.402 seconds
So, if you are going to do multiple operations on the data in a node it is better to copy it over once (if you have the memory).
Labels:

Comments

Post a Comment

Popular posts from this blog

A note on Python's __exit__() and errors

Python's context managers are a very neat way of handling code that needs a teardown once you are done. Python objects have do have a destructor method ( __del__ ) called right before the last instance of the object is about to be destroyed. You can do a teardown there. However there is a lot of fine print to the __del__ method. A cleaner way of doing tear-downs is through Python's context manager , manifested as the with keyword. class CrushMe: def __init__(self): self.f = open('test.txt', 'w') def foo(self, a, b): self.f.write(str(a - b)) def __enter__(self): return self def __exit__(self, exc_type, exc_val, exc_tb): self.f.close() return True with CrushMe() as c: c.foo(2, 3) One thing that is important, and that got me just now, is error handling. I made the mistake of ignoring all those 'junk' arguments ( exc_type, exc_val, exc_tb ). I just skimmed the docs and what popped out is that you need to return True or...
Post a Comment
Read more

Remove field code from Word document

e.g. before submitting a MS, or hand manipulating some formatting because Word does things (like cross-references) so half-assed [from here ] Select all the text (CTRL-A) Press Ctrl+Shift+F9 Editing to remove anonymous comments that only contain thanks. I really appreciate the thanks, but it makes it harder to find comments that carry pertinent information. I'm also going to try and paste informative comments in the body of the post to make them easier to find.
24 comments
Read more

h5py and multiprocessing

The HDF5 format has been working awesome for me, but I ran into danger when I started to mix it with multiprocessing. It was the worst kind of danger: the intermittent error. Here are the dangers/issues in order of escalation (TL;DR is use a generator to feed data from your file into the child processes as they spawn. It's the easiest way. Read on for harder ways.) An h5py file handle can't be pickled and therefore can't be passed as an argument using pool.map() If you set the handle as a global and access it from the child processes you run the risk of racing which leads to corrupted reads. My personal runin was that my code sometimes ran fine but sometimes would complain that there are NaNs or Infinity in the data. This wasted some time tracking down. Other people have had this kind of problem [ 1 ]. Same problem if you pass the filename and have the different processes open individual instances of the file separately. The hard way to solve this problem is to sw...
Post a Comment
Read more