Earlier quoted context omitted.
MemSQL CEO here. There are a few: - MemSQL is transactional and writes transactions on disk - MemSQL has an excellent implementation of SQL with mature query optimization and query execution. And it get better every release. This is from 6.5 https://www.memsql.com/blog/6.5-performance/ - MemSQL has in-memory and on-disk data storage so you can use MemSQL to store petabytes - MemSQL has columnstores and vectorized que…
Given the availability of open source solutions why would I in 2018 build a critical part of my application on a closed platform? Genuinely not intended as snark, I'm just curious why memsql is so compelling that I would consider it.
MemSQL is now free to use for databases with up to 128GB of RAM usage
41–50 of 121 posts
Re: MemSQL is now free to use for databases with up to 128GB of RAM usage
#42Sort of shameless plug, but if you are looking into such solution you could have a look also at https://redisql.com/ It is a redis module that embed SQLite, bringing on the table a lot of advantages. Extremely fast and with it you can even upgrade your Redis instance to be your only database. There is not a huge company behind it, but I really do my best to support it. I don't believe to have disappointed any of our…
Re: MemSQL is now free to use for databases with up to 128GB of RAM usage
#43Re: MemSQL is now free to use for databases with up to 128GB of RAM usage
#44How is MemSQL for OLTP nowadays? Has anyone had any success consistently/scalably using it for true HTAP-ish use cases?
Re: MemSQL is now free to use for databases with up to 128GB of RAM usage
#45This might be a stupid question, but what is the advantage of this solution over an in-memory sqlite database?
Re: MemSQL is now free to use for databases with up to 128GB of RAM usage
#46I don't understand the high frequency use case they describe. High frequency trading is something very different from "12,000 transactions a minute". What is exactly the use case? Pre-deal checks? Post-deal checks? Book replay? Or is it just a simulation? It's not very clear.
HFT can easily be 12000 transactions a minute with a requirement for each of these transactions to be very fast. It's not (necessarily) about high throughput, but about low latency.
I guess you could be using MemSQL for post-order or trade analysis but then it would probably overkill since a lot of that can be done considerably slower.
Re: MemSQL is now free to use for databases with up to 128GB of RAM usage
#47This might be a stupid question, but what is the advantage of this solution over an in-memory sqlite database?
Re: MemSQL is now free to use for databases with up to 128GB of RAM usage
#48This might be a stupid question, but what is the advantage of this solution over an in-memory sqlite database?
They are entirely different systems. Sqlite is meant for self-contained applications that need some relational data persistence with a single file for storage, not for accessing as a central database with many clients storing TBs and scaling across nodes.
Re: MemSQL is now free to use for databases with up to 128GB of RAM usage
#49This might be a stupid question, but what is the advantage of this solution over an in-memory sqlite database?
Distributed. Scalable. OLTP + OLAP queries. High availability. Very fast performance for reads and writes. They are entirely different systems. Sqlite is meant for self-contained applications that need some relational data persistence with a single file for storage, not for accessing as a central database with many clients storing TBs and scaling across nodes.
(Quote from their docs)
Re: MemSQL is now free to use for databases with up to 128GB of RAM usage
#50is memSQL a replacement for a full RDBMS in your stack ? Or just for analytics -- siphoning off the data from your master.