MemSQL is now free to use for databases with up to 128GB of RAM usage
1–10 of 121 posts
Re: MemSQL is now free to use for databases with up to 128GB of RAM usage
#2is memSQL a replacement for a full RDBMS in your stack ?
Or just for analytics -- siphoning off the data from your master.
Re: MemSQL is now free to use for databases with up to 128GB of RAM usage
#3is memSQL a replacement for a full RDBMS in your stack ? Or just for analytics -- siphoning off the data from your master.
MemSQL is an "HTAP" (hybrid transactional-analytical processing) database. They have an in-memory row store table engine for the transactional queries and a disk-backed column store table engine for the analytical queries.
Re: MemSQL is now free to use for databases with up to 128GB of RAM usage
#4Sweet!
Re: MemSQL is now free to use for databases with up to 128GB of RAM usage
#5is memSQL a replacement for a full RDBMS in your stack ? Or just for analytics -- siphoning off the data from your master.
[deleted]
Re: MemSQL is now free to use for databases with up to 128GB of RAM usage
#6Does the free version supports Horizontal sharding and async/sync DISK writes for data mirroring from RAM ?
Re: MemSQL is now free to use for databases with up to 128GB of RAM usage
#7The bit I can't see on the FAQ is about how it is as fast as RAM but protects against data loss using disk.
I think most engines guarantee Durability by assuming that once on disk, it won't go anywhere but if it's in RAM, it is susceptible to power outage? If it gets written to disk, it's not as fast as RAM?
Re: MemSQL is now free to use for databases with up to 128GB of RAM usage
#8What is the benefit of using MemSQL over some other free in memory databases like Apache Ignite ? I see that they have better documentation and support (edit: + competition on Codeforces which winners rarely receive their T-Shirts). What about other things?
Re: MemSQL is now free to use for databases with up to 128GB of RAM usage
#9Does the free version supports Horizontal sharding and async/sync DISK writes for data mirroring from RAM ?
From the announcement:
> You can do almost anything with MemSQL, using the free tier, that you can do if you have an Enterprise license, including capabilities and production use. The differences are that you can only configure the free tier of MemSQL to use up to 128GB of RAM usage, and support is only community support; for paid MemSQL support, you need an Enterprise license.
Re: MemSQL is now free to use for databases with up to 128GB of RAM usage
#10The bit I can't see on the FAQ is about how it is as fast as RAM but protects against data loss using disk. I think most engines guarantee Durability by assuming that once on disk, it won't go anywhere but if it's in RAM, it is susceptible to power outage? If it gets written to disk, it's not as fast as RAM?
The concept in databases that you’re looking for is called group commit. Transactions running concurrently batch writes together before flushing to disk. This means the minimum latency for committing a transaction is the speed of fsync, but the throughput can be as high as the disk bandwidth.
There are other reasons why an in memory database can run faster than a disk based database, such as not having a buffer pool manager, but I don’t think that’s what you were worried about.