mtravis

8 ms·

1.
by mtravis 13y ago
On balance, it will probably be better for you in the long run. I am a high school and college dropout, and nearly as old as dirt. I am entirely self-taught with computers, with no academic credentials. I didn't even take CS courses wh
2.
by mtravis 13y ago
I am having trouble locating any reports to reproducible benchmarks that back up their performance claims.
3.
by mtravis 13y ago
Cool. The wire protocol is PostgreSQL's, so they provide the clients (BSD).
4.
by mtravis 13y ago
This you? http://favstar.fm/users/hipsterhacker Also, the main application is in C++. A python script launches the C++ daemons. Perl scripts are quick and dirty tests and deployment scripts. The main hacking I'm l
5.
by mtravis 13y ago
Thank you, Phil. I'm conflicted about this--I was convinced recently to move away from AGPL having to do with what I was previously unaware of as seemingly legitimate acceptance issues. I feel good about using GPL instead of AGPL. But
6.
by mtravis 13y ago
Good thinking, but I think that shifts the issue--namely, that each inter-thread message uses atomic compare and swap to create the message. I assume there'd be a similar bottleneck on the actor that generates the transactionid limited
7.
by mtravis 13y ago
For durability, check out http://www.infinisql.org/docs/overview/#idp37053600 I've thought about having an actor library, or minimally, to have the actor basis of InfiniSQL independent of specific workload, b
8.
by mtravis 13y ago
Congratulations! Do you have benchmark reports?
9.
by mtravis 13y ago
I think you mean 2PL. It does really scale, check out the benchmark report on the blog. http://www.infinisql.org/blog/2013/1112/benchmarking-infinis... For deadlock-prone workloads, it will likely not be as g
10.
by mtravis 13y ago
1) persistence: battery-backed UPS and synchronous replication. No WAL anywhere. I'm thinking about ways to do disk-based storage without synchronous IO, to provide decent performance with higher storage capacity 2) no joins supported
11.
by mtravis 13y ago
Thanks, edited.
12.
by mtravis 13y ago
Vertica's a data warehouse. InfiniSQL is geared for OLTP. --------- Thanks, jacob019. Please fork/follow on github, twitter if you're into that, etc.
13.
by mtravis 13y ago
On backlog to fix. But InfiniSQL is for hackers and early adopters at this stage. The SQL support is documented ( http://www.infinisql.org/docs/index/ )
14.
by mtravis 13y ago
I assume these shops have Linux in their environments, including the GNU toolchain. There must be some contradiction somewhere that I'm not aware of. Based on FSF feedback, I'm going to modify the license to include a Classpath-li
15.
by mtravis 13y ago
A few things (I'm the author of InfiniSQL) 1) I include keystore-like stored procedures in the source. They do get/set with integer key and string val. I haven't done thorough benchmarking, but I expect them to outperform the
16.
by mtravis 13y ago
Those are analytics databases, also known as data warehouses. Optimized for batch reporting. InfiniSQL is geared for operational/transactional (OLTP) kinds of workloads.
17.
by mtravis 13y ago
Here is some back of napkin analysis: Starting with this benchmark report: http://www.percona.com/files/white-papers/clustrix-tpcc-mysq... Basically, InfiniSQL does not currently support complex indices, so it can
18.
by mtravis 13y ago
Well, array=battery backed controller with a bunch of disks hanging off of it. Actually, there is latency associated with every sync. What I've seen on HDS arrays with Linux boxes and 4GB fibre channell adapters is about 200us per 4KB
19.
by mtravis 13y ago
Hi, eksmith. I talk a bit about plans for durability in that overview document. I promise that I have every intention of making InfiniSQL a platform that does not lose data. I have a long career working in environments that demand 100% data
20.
by mtravis 13y ago
I totally agree--the architecture I'm calling for is to have redundant UPS's, each managed by InfiniSQL processes--for ultimate availability. If people just want high performance but want to live with a datacenter / cloud pro
21.
by mtravis 13y ago
Hi, Leif. It's not hard to get to the throughput limits of a single log device, even on a fast array. I've done it on Sybase, WebSphere MQ, Oracle, MySQL, basically on enough platforms that I assume it to be the general case. The
22.
by mtravis 13y ago
Thanks!
23.
by mtravis 13y ago
Oh, the infinisql_*.h is because I deploy all header files as part of "make install", when what I really should do is boil it down to just the api header. The api is for stored procedure programming. Yes, I have it on backlog to f
24.
by mtravis 13y ago
Your advice that I create formal academic-style paper is reasonable, and I agree that it should be something that I pursue. Will you follow me somehow (by links at http://www.infinisql.org ) so that when such is produced, you&#x2
25.
by mtravis 13y ago
Hi, amalag. Yes, Clustrix is very similar to InfiniSQL (not to mention having been around longer). I believe that InfiniSQL has vastly higher performance at least for the type of workloads that InfiniSQl is currently capable of. InfiniSQL
26.
by mtravis 13y ago
Well, split brain means two parts think they're both active. At that point, nothing can be done (short of manual intervention), because both parts are faulty, and likely, a bunch of others are failed. But, to avoid split brain in a fai
27.
by mtravis 13y ago
Redundancy, quorum protocol, proactive testing, rigorous QA. And actual 24x7 environments with important data are ludicrously expensive. I expect InfiniSQL to be less expensive since it's based on x86_64, Linux, is open source. But yea
28.
by mtravis 13y ago
Oh, I thought you said 2PC (two-phased commit). Yes, InfiniSQL uses two phase locking. The Achilles' Heel is deadlock management. By necessity, the deadlock management will need to be single-threaded (at least as far as I can figure).
29.
by mtravis 13y ago
I'll consider this--meantime, will you please follow me on Twitter and/or sign up for the newsletter, so that you can be informed when the document is ready?
30.
by mtravis 13y ago
Redundant components and pathing, properly implemented and managed, are what allow enterprise storage arrays, mainframe clusters, Tandems, and the like, to operate 24x7 for years on end. Their myth seems to work.

More ›