[IPython-dev] On sqlite history performance improvements...

Thomas Kluyver takowl at gmail.com
Sat Apr 9 18:39:10 EDT 2011

Fernando, try this branch:


There are some issues in the tests (I guess it's race conditions with
history access). I must say, I don't much like this approach. Apart from the
race conditions, we need a separate connection to the database for the
thread, which then has to passed as an argument to every function called
from that thread... I'm sure it can be done, but it's a significant extra
source of potential problems. Indeed, one of the motivations for my history
refactor was to remove the need for a thread to save history...

How slow is the system on which you're seeing noticeable delays? If we
changed the defaults so that we're saving on every 5th or 10th command,
rather than after every command, would the delay be acceptable?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20110409/ec399410/attachment.html>

More information about the IPython-dev mailing list