redis VS cachegrand

services: - type: web name: myapp-web env: ruby region: frankfurt # or oregon plan: starter numInstances: 1 buildCommand: ./bin/render-build.sh startCommand: REDIS_URL="redis://${REDIS_HOST}" bundle exec puma -C config/puma.rb domains: - example.com # replace with your domain name envVars: - key: DATABASE_URL fromDatabase: name: myapp-db property: connectionString - key: REDIS_HOST fromService: name: myapp-redis type: pserv property: hostport - key: RAILS_MASTER_KEY sync: false - type: worker name: myapp-sidekiq env: ruby region: frankfurt # or oregon plan: starter buildCommand: bundle install && bundle exec rake assets:precompile startCommand: REDIS_URL="redis://${REDIS_HOST}" bundle exec sidekiq -e production envVars: - key: DATABASE_URL fromDatabase: name: myapp-db property: connectionString - key: REDIS_HOST fromService: name: myapp-redis type: pserv property: hostport - key: RAILS_MASTER_KEY sync: false - type: pserv name: myapp-redis env: docker region: frankfurt # or oregon repo: https://github.com/render-examples/redis.git numInstances: 1 disk: name: myapp-redis-data mountPath: /var/lib/redis sizeGB: 1 databases: - name: myapp-db plan: starter region: frankfurt # or oregon

Closest that comes to my mind is CacheGrand. It doesn’t have some of the features yet, but I believe @daniele_dll is working on it!

I use this HW for benchmarking and testing my open source project cachegrand ( https://github.com/danielealbano/cachegrand)

https://github.com/danielealbano/cachegrand/blob/main/docs/a...

When tested with memtier_benchmark, using the Redis protocol, cachegrand itself, on the benchmarking hardware, thanks to the implemented hashtable can reach up to 5 million GET op/s and up to 4.5 million UPSERT op/s without batching, with it up to 60 million GET op/s and up to 26 million UPSERT op/s!