SingleStore, every mention

mentionsepisodesper episode tap a year for its mentions

Verbatim, from the transcripts: the passages where SingleStore comes up

loading…

▶ 4:32 Jordan Tigani Because the thing about the way we designed systems, like I was one of the people that helped start Google BigQuery, uh, and I worked on, you know, single store for a couple of years.
▶ 10:28 Jordan Tigani That, um, you know, a big bank did some benchmarking against BigQuery Snowflake and Singlestore when I was at Singlestore, and they kind of, they estimated that on a per core basis, uh, BigQuery was 40 times less efficient than, um, than… 2 times in the scene
▶ 18:53 Jordan Tigani I saw a tweet of, uh, of somebody, um, I was, I was still at single store, and it was doing some bench, somebody was doing some benchmarking of single store against, uh, 2 times in the scene
▶ 32:54 Jordan Tigani Um, you know, MemSQL became SingleStory, which is where I, I worked, I worked previously, um, but I think it turns out that, you know, people really want, you know, they want, they want persistence, they want, you know, if they have,
▶ 56:28 Jordan Tigani And then I jumped into the, into the, you know, deep end at single store, uh, as the chief, chief product officer,

▶ 14:47 Matt Turck So that's, that would be, you know, MemSQL and Recorded Futures at Machine, which are slightly older investments.

▶ 10:17 M.C. Srivas Uh, and then they married it together, and you lost all the consistency, and they said, alright, that's okay, we'll call it MySQL, and, or sorry, memsql, or whatever, no, sorry, that's a different company.

▶ 7:39 Eric (MemSQL) Um, launched the product just this year in June, um, and, you know, been busy sort of, uh, you know, expanding on the next phase of M-SQL.
▶ 9:30 Eric (MemSQL) Um, the whole concept of MemSQL is that you don't need a cache if you can put your data in memory and still use it, you still put it on disk as a, as an archival mechanism.
▶ 11:34 Eric (MemSQL) Um, but fundamentally, uh, I don't think MemSQL would exist if we had to go into it the open source way.
▶ 18:26 Eric (MemSQL) Um, so whenever you go with MM-SQL on EC-II, for example, you will see, like, one millisecond response times, and a Postgres or a MySQL is on the order of 60.
▶ 22:20 Carter Schoenwald And so, one thing I'm wondering, and perhaps the most interesting answer might be from the mem sql guy, um, I'm blank, I'm terrible with names, um, is Eric. 2 times in the scene
▶ 34:09 Matthew Rutley Um, why, why should I use MemSQL over MongoDB?

Turn any episode into a week of clips.