5 ms·
Last time I looked, the SQL layer was really slow. I know they invested a ton of effort to improving it, but I don't think they ever really cracked the problem
by jfindley 8y ago
Last time I looked, the SQL layer was really slow. I know they invested a ton of effort to improving it, but I don't think they ever really cracked the problem and I think you're likely better off with CockroachDB, as mentioned in another reply.
- fizx 8y agoI've built a toy SQL database before that actually did a good job with query planning and used existing highly optimized storage engines (lucene or rocksdb). It was slow AF, because the actual query execution has a ton of method dispatches, etc to e.g. check index conditions or assemble rows and it never quite gets fully JIT'd by the JVM. Every reasonable SQL engine i'm aware of compiles queries to lower-level code. A cursory inspection of their code indicates they don't do this, so its not surprising its slow.
- carlhjerpe 8y agohttps://github.com/jaytaylor/sql-layer https://github.com/jaytaylor/sql-layer Here's the old layer :)