Why MGET is not supported? about rb HOT 4 CLOSED

What would be possible would be to internally automatically use MGET when it makes sense. My tests however did not indicate that MGET would be any more performant than pipelined GET.

from rb.

MGET would be one simpler and handier API. Of course everyone could also do it like this:

def mget(keys):
    results = []
    with cluster.map() as client:  # Assume internally use MGET and assume it is faster
        for key in keys:
            results.append(client.get(key))
    return map(lambda p: p.value, results)

Well, to keep the library clean, you are right :)

from rb.

So I implemented this in two independent layers now.

First of all multiple GET and SET will internally be auto merged into MGET, MSET on the pipeline level. Regardless of if you are using .get or .mget. Secondly promise based clients (like the mapping one) will have an emulated mget / mset command that internally issues multiple get/set calls.

from rb.

👍

from rb.