Python concurrency
Submitted by dv on Sun, 2008-05-04 10:58.
Part of the reason why pjs pjabberd only works on a single processing unit (core) right now is because of the GIL in Python. The architecture uses the asyncore module (asynchronous, like twisted). Looks like it was a good choice, though. In Concurrency with Python, Twisted, and Flex Bruce Eckel demonstrates how he got extreme parallelism from Python+Twisted by spawning n python interpreters, where n is the number of processing units on a machine, and communicating between them via sockets. The Flex part can be mostly ignored. This will come in handy for pjabberd when we add support for multiprocess operation and clustering.
Trackback URL for this post:
http://glyphy.com/trackback/35
Archives
| August 2008 | ||||||
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
| 1 | 2 | |||||
| 3 | 4 | 5 | 6 | 7 | 8 | 9 |
| 10 | 11 | 12 | 13 | 14 | 15 | 16 |
| 17 | 18 | 19 | 20 | 21 | 22 | 23 |
| 24 | 25 | 26 | 27 | 28 | 29 | 30 |
| 31 | ||||||
Recent comments
- Whoops
17 weeks 2 days ago - You can script the
17 weeks 2 days ago - Yep, I’m aware of that
28 weeks 5 days ago - I assume you’re aware of
28 weeks 6 days ago - loob
34 weeks 1 day ago










Post new comment