| |||||||||||||
Backing up in trees with Obnam 1.0Backing up in trees with Obnam 1.0Posted Jun 8, 2012 10:19 UTC (Fri) by rbrito (subscriber, #66188)In reply to: Backing up in trees with Obnam 1.0 by juliank Parent article: Backing up in trees with Obnam 1.0
I was under the impression that even programs written in Python can use multiple cores/cpus/whatever when calling C-extensions (appropriately marked with Py_BEGIN_ALLOW_THREADS/Py_END_ALLOW_THREADS), but I am a real beginner with respect to python and I would appreciate any correction.
(Log in to post comments)
Backing up in trees with Obnam 1.0 Posted Jun 8, 2012 10:32 UTC (Fri) by juliank (subscriber, #45896) [Link]
Yes, but then, this code does not really have much C parts from what I remember.
Backing up in trees with Obnam 1.0 Posted Jun 14, 2012 15:23 UTC (Thu) by JanC_ (guest, #34940) [Link]
Well, all file I/O and a bunch of other things are in C, but all (or most of) that code probably isn't very CPU-intensive...
It should be possible to move the CPU-intensive parts (all the hashing & encryption parts) to C or Cython code. Alternatively, PyPy is working on removal of the GIL, but that might take years to finish.
But I'm not sure in how far Obnam currently uses non-sequential code anyway?
|
|||||||||||||