AdamProut

9 ms·

1. 61.▲
   by AdamProut 5y ago

   Clickhouse is by far the leading open source columnar SQL data warehouse at this point. We have had strong open source operational SQL DBs for many years (MySQL, Postgres), but no open source systems that mirrored closed source MPP columns
2. 62.▲
   A More Flexible Design for Separation of Storage and Compute(singlestore.com)

   1 points by AdamProut 5y ago|0 comments
3. 63.▲
   by AdamProut 5y ago

   I don't think CockroachDB supports anything other then serializable isolation level, so of course they are going to be pushing this type of argument. Its an interesting philosophy really. It would be one thing if the performance penal
4. 64.▲
   by AdamProut 5y ago

   Did any of the actual benchmark queries in TPC-H or TPC-DS show a speed up? My intuition is that the performance of large sorts (100 millions of rows) are not that important for most analytical workloads compared to the performance of doing
5. 65.▲
   by AdamProut 5y ago

   If your building software as a service that changes this calculus a fair bit. You only need to wait for AWS/Azure/GCP/CSP of choice to support the hardware (you don't need to wait for mass market use of it). For example
6. 66.▲
   by AdamProut 5y ago

   Could be: https://tracker.ceph.com/issues/24744 I know this bug has hampered our use of ceph at singlestore. Note that this is not an eventual consistency issue. When it happens the list command will permanently miss
7. 67.▲
   by AdamProut 5y ago

   We have something similar to that at Singlestore (formerly memsql). We support secondary keys and compression schemes that are incremental so you can decompress a few rows out of our columnstore without needing to decompressing the data fo
8. 68.▲
   Lessons from a Journey of Database Discovery(twitter.com)

   33 points by AdamProut 6y ago|1 comments
9. 69.▲
   by AdamProut 6y ago

   I wonder how this approach will compare with an LSM tree style index that has gained popularity recently (mostly via RocksDB). LSM trees are also write optimized and allow for some optimizations by batching up updates and merging them in b
10. 70.▲
    by AdamProut 6y ago

    Yes
11. 71.▲
    by AdamProut 6y ago

    This use case sounds like a good match for MemSQL at a high level (analytics with an SLA is our bread and butter). We'll also have a lot of elasticity features of snowflake shortly without sacrificing our performance advantages. ( http
12. 72.▲
    by AdamProut 6y ago

    As someone who has built a columnstore database and tested it on that query shape (group-by over a column with only a few distinct values) Its possible to go faster than 1 cycle per row via SIMD and operating directly on compressed data (0.
13. 73.▲
    by AdamProut 7y ago

    I'm guessing the use cases they see don't involve query shapes that need to scan a lot of data. A columnstore along with vectorized or batched execution is a much better storage layout for fast scans with filters and aggregation
14. 74.▲
    by AdamProut 7y ago

    I think the ask was for comparisons against traditional analytics databases (redshift, Vertica, etc.). Columnstores are substantially faster for table scans + aggregations then rowstores (and they use a lot less storage) [1]. [1] http:&#x
15. 75.▲
    by AdamProut 7y ago

    Thank you for the the details. Its pretty clear at this point that its not a fair comparison. The TPC-C driver we used (Percona's MySQL TPC-C driver) is pushing MemSQL as hard as it can and isn't following the "think time&qu
16. 76.▲
    by AdamProut 7y ago

    (MemSQL CTO here) 1. MemSQL is running with synchronous replication in all these benchmarks. All data is stored on a 2nd machine before any transaction is acknowledged as committed. You’re right this is not as strong as running with both
17. 77.▲
    by AdamProut 7y ago

    You need columnstore storage and a reasonably mature query optimizer to get good results on TPC-DS. TiDB is lacking both right now.
18. 78.▲
    by AdamProut 7y ago

    MemSQL can run both types of workloads. That is one the main things we're trying to demonstrate by running one of the most popular operational database benchmarks (TPC-C) as well as the two most popular analytics benchmarks (TPC-DS, T
19. 79.▲
    by AdamProut 7y ago

    (MemSQL CTO here) You're right, MemSQL doesn't support foreign keys as of yet, but none of these benchmarks require foreign key support. Two of them (TPC-H and TPC-DS) are a set of complex SELECT queries where foreign keys are no
20. 80.▲
    by AdamProut 7y ago

    (MemSQL co-founder here) How can I not respond to that! As far as I know we've only faced off against TimeScaleDB on one small account in the IoT space. You can't really compare columnstore storage (MemSQL) to rowstore storage (Ti
21. 81.▲
    by AdamProut 15y ago

    Exactly - The entire MySQL ecosystem remains at your disposal when using MemSql.