Skip to main content

Python subprocess, Popen and PIPE

Typically when using Python's subprocess we use PIPEs to communicate with the process. However, it turns out, PIPEs suck when the data gets even slightly large (somewhere in the vicinity of 16K). You can verify this by running the following test code:
from subprocess import Popen, PIPE
import argparse, time

def execute(n):
  p = Popen(['python', 'test.py', '-n', str(n)], stdin=PIPE, stdout=PIPE, stderr=PIPE)
  p.wait()
  return p.stdout.read().splitlines()

if __name__ == "__main__":
  parser = argparse.ArgumentParser()
  parser.add_argument('-n', type=int)
  args = parser.parse_args()
  if args.n is not None:
    print '0'*args.n
  else:
    for n in [10,100,1000,10000,12000,16000,16200, 16500]:
      t0 = time.clock()
      execute(n)
      print n, time.clock() - t0
The output is
10 0.001219
100 0.001254
1000 0.001162
10000 0.001362
12000 0.001429
16000 0.001305
16200 0.00121
(Hangs after this)
The way to handle this is to generate a temporary file and let the process write to the file. A detailed note can be found here.
def execute_long(n):
  with open('query.txt','w') as stdout:
    p = Popen(['python', 'test.py', '-n', str(n)], stdin=PIPE, stdout=stdout, stderr=PIPE)
    p.wait()
  with open('query.txt','r') as stdout:
    return stdout.read().splitlines()

if __name__ == "__main__":
  parser = argparse.ArgumentParser()
  parser.add_argument('-n', type=int)
  args = parser.parse_args()
  if args.n is not None:
    print '0'*args.n
  else:
    for n in [10,100,1000,10000,12000,16000,16200, 16500]:
      t0 = time.clock()
      execute_long(n)
      print n, time.clock() - t0
10 0.001601
100 0.001263
1000 0.001272
10000 0.001404
12000 0.001419
16000 0.001333
32000 0.001445
64000 0.001692
128000 0.001763

Comments

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...

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.

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...