jhugg

26 ms·

211.
by jhugg 12y ago
> Sure, but isn't that basically what everyone does? All of the relational databases I know use ordered key-value storage engines. FoundationDB is the same, except it's distributed. > The point is to use FDB as a foundation.
212.
by jhugg 12y ago
It seems they offer per-key transactions. VoltDB offers full transactions / open-source. Lots of differences between us and Aerospike / FDB.
213.
by jhugg 12y ago
This just lines up with what we've seen in the KV space over the last 5 years. Mutating data and key-lookup are all well and good, but without a powerful query language and real index support, it's much less interesting. Quoting t
214.
by jhugg 12y ago
I think this would still work for that scenario. To beat it, you'd need like-bots that only liked/upvoted one or two sponsored things, then never did again. An algorithm like this would at least prevent you from re-using like-bots
215.
by jhugg 12y ago
This is really cool, but using coin flips really colors the answers. For example, if you pick the Broncos to win out, then it says they have a 75% chance of being the #1 AFC seed. 75% is obviously the chance Patriots will lose one or both o
216.
by jhugg 12y ago
It's a bit unfair to pick on a 2-yr old post, but I don't agree with what Josh is saying here, beyond the fact that anyone claiming to be the world's fastest database is talking about a particular benchmark that makes them lo
217.
by jhugg 12y ago
I think the only device that can't update to iOS 8 is the iPhone 4, which is a bit long in the tooth. I'm guessing Apple isn't going to throw a bone to people who won't update their phones. I doubt they'll help the
218.
by jhugg 12y ago
If @3x is a thing, wouldn't 1080p be kind of an Occam's Razor resolution for a 4.7 device? Besides the fact that 1080p is common and marketable, it would be the perfect resolution to mirror to an AppleTV. And having both the 4.7 &
219.
by jhugg 12y ago
Assume Nest has 10 million users, which is ballpark-ish. 100TB is 10megs per user per day. That sounds high unless my Nest is sending audio clips to Google. I'm sure there are some IoT apps sending 1PB/day, but there are plenty th
220.
by jhugg 12y ago
Do you have a source on the Netflix number? Not doubting, just curious... Also, to nitpick, these are not transactions; these are "operations" or some other word that doesn't imply what the word "transactions" impli
221.
by jhugg 13y ago
Apologies for the curt response, but VoltDB is an existence proof that this isn't necessarily true.
222.
by jhugg 13y ago
VoltDB currently requires stored procedures for multi-statement transactions, but you can send single-statement ad-hoc queries to it just fine (JDBC/Native Clients/HTTP-JSON). Our SQL has gotten significantly more sophisticated la
223.
by jhugg 13y ago
Two things to point out as a VoltDB engineer. 1) VoltDB's global transactions are much slower than its partitioned transactions, but it's relative. It can still do hundreds or thousands per second. 2) Making this number faster for
224.
by jhugg 14y ago
If they posted the config and code, we could probably figure it out.
225.
by jhugg 14y ago
There is an explanation for this. VoltDB latency is currently sub-millisecond for single-node deployments, but often several times higher for clusters. This is due to the current system of global-ordering-agreement that adds some latency. S
226.
by jhugg 14y ago
This.
227.
by jhugg 14y ago
VoltDB Engineer here. It seems like the authors made some unfortunate choices in the configuration and usage of VoltDB. A limited number of synchronous loads are always going to present scalability problems and will do a poor job measureing
228.
by jhugg 14y ago
Is it listed anywhere which versions of MySQL and MongoDB were run?
229.
by jhugg 14y ago
Since 2.0, the journal is enabled. It flushes to disk every 100ms. Operations can return successfully without writing the data to disk. This is similar to what MemSQL is offering by default.
230.
by jhugg 14y ago
Yes, they compile SQL statements into linux binaries using a bundled GNU compiler toolchain. I am also curious if there is some way the developers have demonstrated the benefits of this approach vs. what other systems do. Most of the CPU ti
231.
by jhugg 14y ago
"If you want to throw an anchor behind a speed boat, you can do it, though we don't recommend it." There's a weird implication here that once you need disk persistence, you might as well give up. Group commit and well tuned, append-focused
232.
by jhugg 14y ago
Congrats to the MemSQL team. It's always validating to see more entrants into the space. The comparison between the two systems is fascinating; the approach taking is really different than VoltDB, but the systems share some similar choices
233.
by jhugg 14y ago
Yes, it's a cluster. I totally concede. I just meant it's not the same kind of clustering as Hadoop/HBase, Vertica, VoltDB, Cassandra, Riak, Greenplum, Netezza, Teradata or even DB2-Cluster. If clustering is a spectrum where Dynamo-style sy
234.
by jhugg 14y ago
I'm very familiar with the TPC-C spec and the problem can't be brushed off with "concurrency!". There are multi-second waits in a large percentage of transactions. Nobody does this in any performant OLTP system today, but sure, concurrency!
235.
by jhugg 14y ago
People take TPC-C seriously because not much has come along that's more useful as a transactional benchmark. There are lots of transactional benchmarks, but they're often flawed in some annoying way and don't serve well as a baseline as TPC
236.
by jhugg 14y ago
A big part of my job is talking to people who have scale pain with legacy systems. I don't know what percentage of the DB market this is, but it's nontrivial and growing fast. Most of the markets I mentioned in the previous comment are near
237.
by jhugg 14y ago
It is, surely, difficult to create a product that is better than Oracle/DB2 in every dimension. These systems have thousands of engineer-years of work baked into them. On the other hand, it's pretty easy to beat these systems by specializin
238.
by jhugg 14y ago
If you count OLTP as "a system that places orders created by people", then you might be right. As a VoltDB eng, we see lots of OLTP workloads that require much more throughput than legacy RDBMs can offer on a single system. How many transac
239.
by jhugg 14y ago
I was really hoping this would put gold-leaf illustrations in the margins of my webpage for me.
240.
by jhugg 14y ago
VoltDB achieves concurrency via scheduling, rather than shared access to data structures. There are concurrency primitives around networking/messaging and transaction scheduling, so there aren't truly ZERO locks in the system as a whole. Th

More ›