Ronen Botzer

This is still being researched and discussed. See this discussion thread: https://discuss.aerospike.com/t/gevent-compatibility-or-async-api/1001

The likely chain of events is that the C client adds async support, which is then used for the clients built around it. Currently the Python client has been measured...

That was measured on enterprise grade bare-metal servers. I'm not sure which instance type of EC2 you're on, but yes, I'd guess its performance will lie somewhere between that on...

The libevent client is asynchronous, but only does basic key-value operations. Yes, we are looking into adding async to the C client, alongside the existing synchronous functionality (similar to the...

I understand that the network roundtrip time that can be reclaimed, but you are still using Python and _your_ code is going to execute significantly slower than the extension code....

@RonRothman @ramrengaswamy In 1.0.56 we're releasing the GIL around the calls to the server, other than ones that involve callbacks (`aerospike.Query.foreach` and `aerospike.Scan.foreach`). Let me know how that works for...

@RonRothman I'd love to hear your feedback when you get the chance.

@chicagobuss it seems that @RonRothman has the >= 1.0.56 client working with gevent.

@chicagobuss well, it definitely shouldn't segfault. :grimacing:

This is on the way for the next version of the Python client.