[Lxml-checkins] r39207 - lxml/trunk/doc

[scoder at codespeak.net]

Author: scoder
Date: Mon Feb 19 15:29:39 2007
New Revision: 39207

Modified:
   lxml/trunk/doc/FAQ.txt
Log:
note on possible speed-up when compiling lxml without threading

Modified: lxml/trunk/doc/FAQ.txt
==============================================================================
--- lxml/trunk/doc/FAQ.txt	(original)
+++ lxml/trunk/doc/FAQ.txt	Mon Feb 19 15:29:39 2007
@@ -73,7 +73,7 @@
 of a pre-installed standard compiler and the missing package management.  Both
 make it non-trivial to build lxml on this platform.  We are trying hard to
 make lxml as platform-independent as possible and it is regularly tested on
-Windows systems.  However, we currently cannot provide Windows binaries
+Windows systems.  However, we currently cannot provide Windows binary
 distributions ourselves.
 
 From time to time, users of different environments kindly contribute binary
@@ -122,10 +122,12 @@
 simplicity of the API might suggest.  The `benchmark page`_ has a comparison
 to other ElementTree implementations and a number of tips for performance
 tweaking.  As with any Python application, the rule of thumb is: the more of
-your processing runs in C, the faster your application gets.
+your processing runs in C, the faster your application gets.  See also the
+section on threading_.
 
 .. _`a few caveats`:  performance.html#the-elementtree-api
 .. _`benchmark page`: performance.html
+.. _threading:        #threading
 
 
 Why do I get errors about missing UCS4 symbols when installing lxml?
@@ -236,6 +238,15 @@
 multi-threading.
 
 
+Would my single-threaded program run faster if I turned off threading?
+----------------------------------------------------------------------
+
+Can be.  You can see for yourself by compiling lxml entirely without threading
+support.  Pass the ``--without-threading`` option to setup.py when building
+lxml from source.
+
+
+
 Parsing and Serialisation
 =========================