John Eckersberg b97b24856f Use eventlet-aware threading events ... For the gory details behind this, see: https://bugzilla.redhat.com/show_bug.cgi?id=1384183 In summary, if you use threading.Event on python2 with eventlet, it unnecessarily spams system calls to epoll_wait and burns a *lot* of CPU cycles by constantly context-switching. I added eventletutils.Event to oslo_utils a while back to intelligently use the eventlet Event object when eventlet is being used, and to fall back to the threading one otherwise. So just use that and it will do the right thing. Depends-On: https://review.openstack.org/#/c/558879/ Change-Id: I6ca0d0fc2a2ff393bab502a5f705fb0d63c32c6b		2019-06-17 13:27:55 +02:00
..
examples	Make rpc_backend not engine specific	2017-04-27 20:02:40 +00:00
__init__.py	Make rpc_backend not engine specific	2017-04-27 20:02:40 +00:00
base.py	Remove remaining references to the rpc_backend	2018-10-12 11:23:50 +07:00
kombu_client.py	[Event-engine] Allow event_engine to work in HA	2018-10-17 16:30:17 +00:00
kombu_hosts.py	Remove remaining references to the rpc_backend	2018-10-12 11:23:50 +07:00
kombu_listener.py	Use eventlet-aware threading events	2019-06-17 13:27:55 +02:00
kombu_server.py	Use eventlet-aware threading events	2019-06-17 13:27:55 +02:00