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

Store numpy arrays in sqlite

Use numpy.getbuffer (or sqlite3.Binary ) in combination with numpy.frombuffer to lug numpy data in and out of the sqlite3 database: import sqlite3, numpy r1d = numpy.random.randn(10) con = sqlite3.connect(':memory:') con.execute("CREATE TABLE eye(id INTEGER PRIMARY KEY, desc TEXT, data BLOB)") con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", sqlite3.Binary(r1d))) con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", numpy.getbuffer(r1d))) res = con.execute("SELECT * FROM eye").fetchall() con.close() #res -> #[(1, u'1d', <read-write buffer ptr 0x10371b220, size 80 at 0x10371b1e0>), # (2, u'1d', <read-write buffer ptr 0x10371b190, size 80 at 0x10371b150>)] print r1d - numpy.frombuffer(res[0][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] print r1d - numpy.frombuffer(res[1][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] Note that for work where data ty...
Post a Comment
Read more