jess
Reputation: 347
In memory MySQL table vs Redis, about insert and concurrency performance
Since data is stored in memory in both cases, is it possible to have the same approximative insert/s and concurrency performance for both?
If not, why?
Upvotes: 8
Views: 4005
Answers (1)
Bill Karwin
Reputation: 562328
Concurrency for the MySQL MEMORY storage engine is not good. Like MyISAM, it can only do table-locks. So all concurrent threads doing inserts queue up against each other.
Upvotes: 10
Related Questions
- Is Redis faster than MySQL?
- How to combine REDIS and MySQL for mass INSERT to get better performances (Real Time)
- SQL Server 2014 In-Memory OLTP vs Redis
- MySQL MEMORY Engine Performance - Concurrent Insert vs Update
- Will REDIS give me fast In-Memory access to recent rows and fallback to a persistent store for long term entries?
- Redis concept: In memory or DB?
- Redis vs Mysql engine type memory
- Mysql MEMORY table vs InnoDB table (many inserts, few reads)
- What's the good choice for handling with real-time data in memory?
- using Redis AOF fsync per write vs MYSQL myism db performance