This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jderose
Recipients barry, jderose, ncoghlan, ned.deily, pitrou
Date 2011-09-07.04:25:58
SpamBayes Score 1.4320742e-05
Marked as misclassified No
Message-id <1315369559.86.0.0446591758896.issue11677@psf.upfronthosting.co.za>
In-reply-to
Content
Barry,

I'm suspicious there might be more to the performance issue than just the ecryptfs overhead.  While experimenting with a read benchmark, I just happened to notice that when reading from an ecryptfs filesystem, the CPU usage is unusually high in the *python3* process.

For example:

./benchmark.py /home/.dmedia
  => 149 MB per second
  => top shows 22-24% CPU usage

./benchmark.py /home/jderose/.dmedia
  => 38.9 MB per second
  => top shows 79-85% CPU usage

It's the same physical drive in both cases, but the one in /home/jderose is ecryptfs.  If it was just ecryptfs overhead, wouldn't there be lower CPU utilization in the python3 process, as there would be a lower throughput coming from the kernel, more time waiting on IO?

In both cases, there were 56 files, for a total of 19.5 GB.  I ran this on 64-bit Ubuntu Oneiric, Python 3.2.2.

Here's the benchmark:

http://bazaar.launchpad.net/~jderose/filestore/multi/view/head:/benchmark.py
History
Date User Action Args
2011-09-07 04:26:00jderosesetrecipients: + jderose, barry, ncoghlan, pitrou, ned.deily
2011-09-07 04:25:59jderosesetmessageid: <1315369559.86.0.0446591758896.issue11677@psf.upfronthosting.co.za>
2011-09-07 04:25:59jderoselinkissue11677 messages
2011-09-07 04:25:58jderosecreate