Long time no write! A while ago I wrote a post about how to combine Twisted with SQLObject. The method describe there, however, doesn’t work particularly well when using SQLite.
Since SQLite databases are a single file (or a memory area) some operations will need to lock when writing. In the other post we used deferToThread, which will run a function on a different thread and return a Deferred which will fire when the operation is finished. The thread on which the operation will be run is taken from the reactor thread pool, so it’s not a single thread. This means that if more than one write operation is executed almost at the same time, the first operation will get the lock, and the others will need to wait. When using SQLObject, the operation will fail if the lock can’t be acquired, so let’s see what we can do about it.
One option would be to use the timeout parameter and set it to some reasonable value, so that the operation would wait that amount of time before giving up on the lock. It’s not 100% guaranteed that it will get it, so this could be complemented with a wait-retry strategy.
Or we can just run all database operations in a single thread. This way only one operation will be executed at a time so we avoid the issue. Also, since we return deferreds nothing will be blocked waiting for results.
In order to do this I chose to use Twisted’s ThreadPoolclass, with a single thread. The reason for doing it this way is that Twisted provides us with nice functions to run operations on one of these pools and return a deferred.
First we setup our thread pool:
[gist]https://gist.github.com/994097[/gist]
We will need to stop the thread pool when our application ends, hence the call to addSystemEventTrigger. It will run the specified function when the reactor is about to be stopped.
The we’ll create a decorator which we’ll use to decorate functions that will run on the thread pool:
[gist]https://gist.github.com/994098[/gist]
Since the thread pool only has a single thread we are effectively serializing all database operations, if they are called using our decorator. Lets see a complete example:
[gist]https://gist.github.com/994096[/gist]
Hope you find it useful!
:wq
Awesome!Thanks for all the great examples for how to set up a threadpool. My backend for Gridspy is going to use this approach to serialise our database connections. I love the idea for using a decorator for this (was using lots of deferToThread calls before).Also, thanks for pointing out addSystemEventTrigger – hadn’t seen that before.Overall, a great tutorial. Thanks :)-Tom
Hi Tom!Glad you like it! I’ll check Gridspy out! 😉