[fusl]

Your benchmarks:

Google's new Cloud Memorystore, 1.0 GB:

    redis-cli -h 10.0.0.3 --intrinsic-latency 100
    677411416 total runs in 100 seconds
    avg latency: 0.1476 microseconds / 147.62 nanoseconds per run

Open-source Redis on a Google Cloud Platform micro instance, 0.6 GB:

    redis-cli -h localhost --intrinsic-latency 100
    353427208 total runs in 100 seconds
    avg latency: 0.2829 microseconds / 282.94 nanoseconds per run

Open-source Redis on an AWS EC2 micro instance, 1.0 GB:

    redis-cli -h localhost --intrinsic-latency 100
    21681751 total runs in 100 seconds
    avg latency: 4.6122 microseconds / 4612.17 nanoseconds per run

My benchmark:

Open-source Redis on a Hetzner Cloud VPS, CX11 (92% cheaper than Google's Cloud Memorystore):

    redisbench-client:~# redis-cli -h 88.99.124.195 --intrinsic-latency 100
    Max latency so far: 1 microseconds.
    Max latency so far: 77 microseconds.
    Max latency so far: 113 microseconds.
    Max latency so far: 130 microseconds.
    Max latency so far: 2562 microseconds.
    Max latency so far: 2835 microseconds.
    Max latency so far: 4165 microseconds.
    Max latency so far: 5497 microseconds.

    757281326 total runs (avg latency: 0.1321 microseconds / 132.05 nanoseconds per run).
    Worst run took 41628x longer than the average latency.

[antirez]

Unfortunately intrinsic latency does not measure the latency of the Redis instance, but the one of the whole host, that is, the kernel scheduler max latency.