> One of the things I mentioned on the c.l.py thread is the > Py_BEGIN_ALLOW_THREADS and Py_END_ALLOW_THREADS calls around every > fwrite() call. I looked into it, using Penrose's test case, and found > that the locking alone added 25% overhead. I expect the layer or two > of C function calls above fwrite() add overhead. I also expect that > calling fwrite() repeatedly for very small strings is inefficient. > > If I were to suggest a cPickle project, it would be an efficient > internal buffering scheme. Who's got time? It's fast enough for Zope. :-) --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4