For something really memory-bound. joneholland's suggestion of Redis seems plausible, and you can imagine other data tasks that are CPU-light but RAM-heavy (mem

For something really memory-bound. joneholland's suggestion of Redis seems plausible, and you can imagine other data tasks that are CPU-light but RAM-heavy (memcache?). And not what you were commenting on, but the larger of the new sizes also provide a bit more flexibility in that space above r4.16xl's RAM capacity, or where the big r4s have excess compute compared to what your DB, etc. really wants. We have some places at work where Python multiprocessing RAM overhead, rather than CPU, is sadly the limiting factor for our concurrent requests/sec., but I doubt it's extreme enough to make x1e attractive for it.