jhugg

29 ms·

241.
by jhugg 15y ago
To update what you've said with insider info, ad-hoc SQL performance is currently a big focus at VoltDB. We fully support ad-hoc access in auto-commit mode through our native clients or through JDBC. Currently, we can do hundreds or thousan
242.
by jhugg 15y ago
VoltDB Community Edition uses synchronous intra-cluster replication, as well as rolling on-disk snapshots for durability. The Enterprise Edition adds a synchronous or asynchronous command log (a logical journal) as well as asynchronous mult
243.
by jhugg 15y ago
You might get a better number on bare metal, and you certainly won't get a worse one, so in a sense it's not ideal. On the other hand, a big chunk of the web is run from AWS. Demonstrating performance there implies performance in many place
244.
by jhugg 15y ago
The connected world is moving away from PCs. Adobe's previous plans were to have Flash be a unifying rich media platform across all these newfangled devices, like TVs, tablets, alarm clocks, etc… Flash could grow as the "connected market" g
245.
by jhugg 15y ago
So running with your example, assume I have a transaction that adds 5 to a column value and then reads the value back. If I start with a value of 0, then run my transaction twice, can both transactions return 5? Or is it guaranteed that one
246.
by jhugg 15y ago
My understanding of the MVCC at work is that writes must effectively be serialized, but that pure-read transactions never have to block, as they can view a consistent snapshot of the state at any time. This would imply read-scaling, but I d
247.
by jhugg 15y ago
Not sure he meant a literal hot spot.
248.
by jhugg 15y ago
Maybe the point was that there are a lot cooler ways to piss away 41m than taking 5 photos at WWDC. Perhaps few of them would sound interesting to a VC though.
249.
by jhugg 15y ago
I disagree. It reads like an engineer who is frustrated that his/her tech is getting out-businessed (perhaps in a slimy way). Engineers generally want to live in a world where the best tech wins, but in the end, we go home to our betamax pl
250.
by jhugg 15y ago
Even if it's hard to disagree with anything specific in the post, who does this tone appeal to? Is the author selling or venting?
251.
by jhugg 16y ago
I think the argument that dumb phones are a huge growth market in the developing world is flawed. It's staggaring how many people have dumbphones already. I suspect the dumber of dumbphones in use will never double again. Smartphones still
252.
by jhugg 16y ago
I stopped reading at, "I don't put too much weight in Apple's iPad app advantage." Sadly, that was in the last paragraph.
253.
Is VoltDB really as scalable as they claim?(mysqlperformanceblog.com)
6 points by jhugg 16y ago|0 comments
254.
by jhugg 16y ago
VoltDB is looking for Summer 2011 interns in Boston area. We're small, so our interns basically become engineers for a few months, and have lots of flexibility on what they want to work on. Also, as an open source company, you can point peo
255.
by jhugg 16y ago
>> When hundreds of companies and thousands of the brightest programmers and sysadmins have been trying to solve a problem for twenty years and still haven’t managed to come up with an obvious solution that everyone adopts, that say
256.
by jhugg 16y ago
RAC uses a shared disk; it doesn't eliminate the single point of failure. The shared disk also adds a contention point, such that RAC often stops scaling after a handful of nodes. Even the first few don't give you linear scalability without
257.
by jhugg 16y ago
I've always been super jealous at how much Chinese speakers can say in Chinese on Twitter.
258.
How VoltDB Does Transaction Ordering and Replication(voltdb.com)
3 points by jhugg 16y ago|0 comments
259.
by jhugg 16y ago
VoltDB relies on syncronous replication to protect data from hardware and network failures. It also supports continuous and transactionally-isolated snapshotting to disk.
260.
by jhugg 16y ago
At VoltDB, we're working on improving our SQL support. Initially, we focused on core SQL useful for OLTP. We've added functionality with every release and we plan to continue in 2011. For example, the March release of VoltDB will support mo
261.
by jhugg 16y ago
Perhaps, but it really depends on what you want to do exactly. You can probably store a lot less and get the same throughput. - VoltDB isn't log-structured, so you really only have to store the state. How fast you can mutate it isn't limite
262.
by jhugg 16y ago
Semi-dup. These are the slides, which may be better than linking to a techcrunch article, but more comments are here: http://news.ycombinator.com/item?id=2180840
263.
by jhugg 16y ago
Shameless self-promotion, but important point nonetheless: VoltDB is truly fantastic at this kind of workload. It's one of the first use cases we had traction with. Also, VoltDB is open source today.
264.
by jhugg 16y ago
Overall, another solid comment. As for RPC, whether the client is informed of success or failure has nothing to do with atomicity. The guarantee is that the transaction either happens completely or not at all, and nothing more. Agreed, it c
265.
by jhugg 16y ago
I like the content of this post, but I take issue with the idea that the debate only matters in a failure condition. That's academically true, but practically misleading. When developing my app, I have to assume any part of the system could
266.
by jhugg 16y ago
The attacks on NoSQL seem a little harsh to me. People needed scalable systems. They needed them ASAP. Nobody in the RDBMS camp was even hinting at products targeting this market. Then, the NoSQL camp built systems that scale (albeit with c
267.
by jhugg 16y ago
Again, replying to a deeper comment. I sure don't disagree with everything you are saying. As for adding transactions to get a balance, yes, this is how the basics work and it doesn't look like ACID at all. However, what you're describing i
268.
by jhugg 16y ago
Replying to the deeper nested comment. 1) I totally concede that you could use Dynamo-style consistency to be the system of record for financial exchanges. I just don't think it's a good idea. I'm not sure anyone building these systems do
269.
by jhugg 16y ago
As for the VoltDB comment, how much we compete with NoSQL or whether we are NoSQL is an interesting line of questions. We're trying to bleed customers away from entrenched systems the same as most NoSQL systems. I think there's plenty to go
270.
by jhugg 16y ago
Quorum writes to Dynamo nodes allow you make atomic and durable updates to single keys and the data associated with them. ACID transactions allow you to mutate data associated with multiple keys atomically. This is not the same thing at all

More ›