Pulsar: Concurrent framework for Python
pythonhosted.org
Pulsar: Concurrent framework for Python
1–10 of 14 posts
Re: Pulsar: Concurrent framework for Python
#2Interesting! Seems like a hyper-framework, a one-fits-all solution for a python backend. I would like to see any benchmarks comparing this to tornado/twisted/nodejs and perhaps an async mongoDB client implementation. Great work anyway!
Re: Pulsar: Concurrent framework for Python
#3Interesting! Seems like a hyper-framework, a one-fits-all solution for a python backend. I would like to see any benchmarks comparing this to tornado/twisted/nodejs and perhaps an async mongoDB client implementation. Great work anyway!
Indeed, I've only taken a quick look, but I like what I see!
Speaking of benchmarks, we'd be very happy to receive a pull request [1] with a test implementation if anyone is interested.
Re: Pulsar: Concurrent framework for Python
#4Will work on Google app engine?
Re: Pulsar: Concurrent framework for Python
#5Finally a concurrency framework that works with Python 3! I will definitely have to check this out, because Twisted is the only thing preventing me from switching (and Gevent doesn't support it either).
Re: Pulsar: Concurrent framework for Python
#6Ha, funny but there is concurrency library (actors, CSP) for Clojure with the same name. http://puniverse.github.io/pulsar/
Re: Pulsar: Concurrent framework for Python
#7Finally a concurrency framework that works with Python 3! I will definitely have to check this out, because Twisted is the only thing preventing me from switching (and Gevent doesn't support it either).
What about concurrent.futures from standard library?
Re: Pulsar: Concurrent framework for Python
#8Interesting! Seems like a hyper-framework, a one-fits-all solution for a python backend. I would like to see any benchmarks comparing this to tornado/twisted/nodejs and perhaps an async mongoDB client implementation. Great work anyway!
Thinking about new tech in term of performance is silly. If you need performance NOW just stick with the known solution because odds are you also need stability and a well tested platform.
Re: Pulsar: Concurrent framework for Python
#9Semiofftopic: Animated favicons are evil. Can't just leave the tab open to take a look at a later time.
Re: Pulsar: Concurrent framework for Python
#10Interesting! Seems like a hyper-framework, a one-fits-all solution for a python backend. I would like to see any benchmarks comparing this to tornado/twisted/nodejs and perhaps an async mongoDB client implementation. Great work anyway!
Thinking about new tech in term of performance is silly. If you need performance NOW just stick with the known solution because odds are you also need stability and a well tested platform.
No, it's not. It's a good indicatior of how performant the framework is likely to be in the future, in the context of ballparks.
For example, if this version already is as quick as comparable software written in C, you know that chances are that it will be even faster in the future and not slower. If it uses an hour to open a port and send a package, that doesn't bode well for future development.