G-Firefly | gevent version , with better perfromance

G-Firefly is a Python library. G-Firefly has no bugs, it has no vulnerabilities and it has low support. However G-Firefly build file is not available. You can download it from GitHub.

####g-firefly简介+firefly-gevent重要迭代版本alpha 0.1.5介绍 在alpha 0.1.5做了如下的改进： １、单node节点断开与root节点的连接后自动重连。 ２、修改了gfirefly的底层库gtiwsted,将socket发送数据放到一个协程中进处理，解决了. 忽略其他因素，gevent性能是线程方案的4倍左右（在这个测试中对比的是paste，译者注：这是python另一个基于线程的网络库） 与单进程多线程模型相比，多进程和协程是更加scalable的模型。在高并发场景下，采用多进程模型编制的程序更加容易scale out，而协程模型可以使单机的并发性能大幅提升，达到scale up的目的。所以，未来服务器端并发模型的标配估计会是：每个核一个进程，每个进程是用协程实现的微线程。. ####firefly-gevent alpha 0.1.2 release – an important version update. firefly-gevent is firefly gevent version which is more of simplicity comparing to current firefly twisted version. based on coroutine, python-written gevent is a web development framework. coroutine is a concurrency model, but unlike to thread and callback, all its tasks can be executed in a single thread, and are able to swap to another task for execution by initial aborting in a task. it has program-level schedule rather than thread’s system-level schedule. amazing performance is gevent’s most obvious feature, especially when you compare it to traditional thread solution. on this point, an almost common sense fact is that asynchronous i/o performance will be significantly superior to separate thread-based synchronous i/o when load is over a certain degree. in the meantime, gevent provides seemingly much alike traditional port that was programmed based on thread model. however this port’s real identity is asynchronous i/o, and what’s more wonderful part is that it makes all these transparent (here it means you don't need to worry about how it function itself, gevent will help you finish the switching job). ignoring other factors, gevent performance is four times greater than thread solution (here in this test we use paste as contrast, note: paste is another thread-based web library of