Live data from Hacker News

MemSQL is now free to use for databases with up to 128GB of RAM usage

memsql.com

11–20 of 121 posts

Re: MemSQL is now free to use for databases with up to 128GB of RAM usage

#11
Sort 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 users so far.

Also the tech documentation: http://redbeardlab.tech/rediSQL/references/

Re: MemSQL is now free to use for databases with up to 128GB of RAM usage

#12
I 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.

Re: MemSQL is now free to use for databases with up to 128GB of RAM usage

#13
post #7

The 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?

It might use a Write-Ahead log like postgres to guarantee data integrity between memory and disk.

Re: MemSQL is now free to use for databases with up to 128GB of RAM usage

#14
post #8

What 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?

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 query processing: https://news.ycombinator.com/item?id=16617098

- MemSQL supports geospatial, fulltext search, and json

- MemSQL allows you to stream data from kafka in one command: https://docs.memsql.com/sql-reference/v6.5/create-pipeline/

Re: MemSQL is now free to use for databases with up to 128GB of RAM usage

#15
I've been using MemSQL in development since March 2017. I've seen it evolve into one of the fastest databases for columnar storage and analytical workloads. Having in-memory rowstore as well removed the need to have Aerospike in my infrastructure and simplified the whole stack.

This announcement, that it's now free to 128GB pretty much saved me from having to do a kickstarter to raise funds for my little SaaS project.

If anyone from MemSQL is reading, really thanks for doing this. I think it's a very shrewd move. Should definitely see an upswing of potential customers adding it to their stack and when they grow, become enterprise customers.

Re: MemSQL is now free to use for databases with up to 128GB of RAM usage

#17
post #7

The 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?

It might use a Write-Ahead log like postgres to guarantee data integrity between memory and disk.

That’s right and it writes it on two separate nodes if u enable high availability

Re: MemSQL is now free to use for databases with up to 128GB of RAM usage

#20

What happens if I set hard limit on MemSQL process to use 128GB RAM and it decides it needs more? Will it die demanding more memory or will it behave like traditional rdbms and manage buffers to work within limits?

The best thing to do in this situation would be to set the maximum memory on the MemSQL server via the `maximum_memory` system variable. The server will then internally manage it's memory usage against this upper bound and fail only specific operations which can't be performed without additional memory.
Post reply on HN