Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MemSQL Launches Unlimited Community Edition

blog.memsql.com

Post reply on HN
Print view View original

31–40 of 56 posts

Re: MemSQL Launches Unlimited Community Edition

#31

Post by ericfrenkiel »

willvarfar wrote: post #30
capkutay wrote: post #24

Earlier quoted context omitted.

I think the FoundationDB acquisition by a company with no interest in selling enterprise products was an anomaly. A popular, commercial enterprise storage system that actually makes money would be an acquisition target from the likes or Oracle, SAP, EMC, etc...in that scenario, the acquiring company would have significant interest to increase adoption of the product and maintain the developer community versus complet…

You mean like Oracle with MySQL? At least in that case the 'community' could move to MariaDB, which is not an option for non-Free databases like MemSQL.

you can do the very same - MemSQL uses the MySQL-wire protocol so it works with any MySQL driver and tool.

Re: MemSQL Launches Unlimited Community Edition

#32

Post by rjonesx »

stock_toaster wrote: post #13

> The Community Edition is distributed as an executable > binary and is a free edition of the commercial MemSQL > Enterprise Edition. You are free to download and use > MemSQL Community Edition within your organization. So.. how long until the same thing happens as happened with FoundationDB?

While I am an enterprise user of memSQL now, I still have a machine running the beta version 1.0 from years back. It is still stable and still fast as hell.

Re: MemSQL Launches Unlimited Community Edition

#33

Post by rjonesx »

mbesto wrote: post #18
ericfrenkiel wrote: post #3

Eric, one of the cofounders, here. happy to answer any questions on MemSQL 4 and the community edition. Some new features in MemSQL 4: - fully distributed joins - native geospatial index and datatypes - lots of new SQL surface area - concurrency improvements - analytic optimizer - Spark, HDFS, and S3 connectors

Hi Eric! Not sure if you remember me, but we spoke several (5?) years ago when you guys first started. I was the SAP HANA guy and I think we were talking about the landscape of in-memory solutions back then. First off, congrats on the success so far. Second, a few questions: - How is MemSQL comparing to HANA and Vertica? My understanding is that MemSQL provides the same infrastructure (columnar in-memory based storag…

"but will run on commodity hardware"

We run memSQL 4.0 on 18 machine cluster, all commodity hardware. It is awesome.

Re: MemSQL Launches Unlimited Community Edition

#34

Post by rjonesx »

aklarfeld wrote: post #11

This is way cool. Already spinning it up on my AWS clusters. Such a quick setup. Super stoked to us it.

It is way cool. I've been an enterprise user for some time now and am excited to get to use it on other projects for which there wasn't cost justification in the past.

Re: MemSQL Launches Unlimited Community Edition

#35

Post by SkidanovAlex »

jamesblonde wrote: post #16
ericfrenkiel wrote: post #3

Eric, one of the cofounders, here. happy to answer any questions on MemSQL 4 and the community edition. Some new features in MemSQL 4: - fully distributed joins - native geospatial index and datatypes - lots of new SQL surface area - concurrency improvements - analytic optimizer - Spark, HDFS, and S3 connectors

Interesting. We've implemented a metadata layer for HDFS and YARN using NDB (MySQL Cluster) - that also supports READ COMMITTED transactions. Do you support: - row-level locking - independent transaction coordinators at data nodes - pruned index scans - network-aware transactions (with user-defined partition keys for tables) - any asynchronous/event API ?

MemSQL partitions data across nodes by hash, not by range, so partition prunning is less applicable. However, in a case when it can be applied MemSQL does apply it. [1]

Within each node, for column store tables in MemSQL we do use segment elimination very aggressively, which is effectively the same thing as partition pruning. [2] [3]

[1] http://docs.memsql.com/latest/concepts/distributed_sql/#inde...

[2] http://docs.memsql.com/latest/concepts/columnar/#query-effic...

[3] http://docs.memsql.com/latest/concepts/columnar/#maintenance...

Re: MemSQL Launches Unlimited Community Edition

#36

Post by rjonesx »

jansc wrote: post #20

> While you are free to use Community for your projects, > MemSQL does not support or endorse using it in production. ( http://blog.memsql.com/memsql-community-edition/ ) Ehhh. Do they mean that the Community Edition is only usable for development?

I currently use beta 1.0 for one of my tools and it has been functioning for years without a problem. I think they are just saying don't sue us if you use in production and didn't pay for it :-)

Re: MemSQL Launches Unlimited Community Edition

#37

Post by DannoHung »

nikita wrote: post #6
DannoHung wrote: post #5

Are there any optimizations or explicit support for proximate ordered joins?

Could you please elaborate? Do you mean approximate joins as in this talk? http://www2.research.att.com/~divesh/papers/ks2005-aj-tutori...

No no, sorry, it's much simpler (at least in how it works, no guarantees on implementation complexity, of course). It's an issue that comes up in timeseries databases pretty often.

Say I have a table full of quotes and a table full of trades. I want to know what the quote price was at the time the trade occurred. In no-frills SQL, that translates into something like:

    select * from t left outer join q on q.time=(select max(time) from q where time
If you have some sort of support for time proximate joining, the query engine only has to perform a binary search (as long as the indices on the symbol and time columns are appropriate, say symbol partitioned, then time sorted within symbol) to find the correct row from quote to join against. If it doesn't have such support, then a scan is required to find the maximum time value from the quote table that satisfies the constraint on the trade time. Presumably, if you do have support, this wouldn't be the exact query syntax, because that would heavily imply that you want to perform a table scan, or that you could change some aspect of the subquery without affecting performance. Maybe you'd have it be something like this:

    select * from t left outer join q on before(t.time,q.time) and t.sym = q.sym where date = d and sym = s

Re: MemSQL Launches Unlimited Community Edition

#38

Post by mbesto »

ericfrenkiel wrote: post #26
mbesto wrote: post #18

Earlier quoted context omitted.

Hi Eric! Not sure if you remember me, but we spoke several (5?) years ago when you guys first started. I was the SAP HANA guy and I think we were talking about the landscape of in-memory solutions back then. First off, congrats on the success so far. Second, a few questions: - How is MemSQL comparing to HANA and Vertica? My understanding is that MemSQL provides the same infrastructure (columnar in-memory based storag…

Of course we remember you. Please stop by our new office! You are right about the commodity hardware. The other difference with HANA is that MemSQL rowstores are in memory for high throughput applications and columnstores can be stored or flash or disks. So it's economical to scale MemSQL to very large datasets. - MemSQL is very easy to scale. It comes with an ops dashboard that lets you add nodes with just a few cli…

I might take you up on that! Shoot me your contact details so I can set up (just did a search on my emails and can't find anything). My contact is in my profile.

Thanks!

Re: MemSQL Launches Unlimited Community Edition

#39

Post by seanp2k2 »

nikita wrote: post #4
phamilton wrote: post #2

Cue "Call me maybe, MemSQL" Aphyr's posts (taken with appropriate amounts of salt) have become the authority on marketing claims. That said, many solutions are perfectly viable with their shortcomings, but knowing what those shortcomings are is essential.

When MemSQL is configured for synchronous durability and all databases are configured with synchronous replication, Jepsen confirms that writes to MemSQL are durable and acknowledged appropriately. As part of testing for the 4.0 release, we used the jepsen network partition test and observed data durability equivalent to Postgres( https://aphyr.com/posts/282-call-me-maybe-postgres ) e.g. the scalability of a cluster…

^ would love to see the details of this in a blog post, yeah. Please submit that on HN when it's ready; I'm sure I'm not the only one interested :)

Re: MemSQL Launches Unlimited Community Edition

#40

Post by nikita »

mbesto wrote: post #38
ericfrenkiel wrote: post #26

Earlier quoted context omitted.

Of course we remember you. Please stop by our new office! You are right about the commodity hardware. The other difference with HANA is that MemSQL rowstores are in memory for high throughput applications and columnstores can be stored or flash or disks. So it's economical to scale MemSQL to very large datasets. - MemSQL is very easy to scale. It comes with an ops dashboard that lets you add nodes with just a few cli…

I might take you up on that! Shoot me your contact details so I can set up (just did a search on my emails and can't find anything). My contact is in my profile. Thanks!

eric at and nikita at memsql.
Post reply on HN