glommer

10 ms·

61.
by glommer 4y ago
Sure am, but chiselstrike is OSS as well. So no different than any OSS project with a monetization strategy. (github.com/chiselstrike/chiselstrike)
62.
by glommer 4y ago
that was exactly the point I was trying to make! One of the things we aim to do with chiselstrike is to allow that transition to happen easily by providing a unifying interface.
63.
by glommer 4y ago
with money! (We work with a design firm that provides illustrations for the blog)
64.
by glommer 4y ago
Erlang is dope!
65.
by glommer 4y ago
I am! but Chiselstrike doesn't sell a message queue, so still don't understand how I'm selling one. It's an abstraction over a message queue, which is only one feature among many. But btw, as a pointy-haired dude I am be
66.
by glommer 4y ago
Hey! OP here. I didn't know I was trying to sell a message queue, thanks for letting me know!
67.
by glommer 4y ago
Curious if you've taken a look at ChiselStrike (disclaimer: founder here) ChiselStrike translates typescript to sql transparently ( https://blog.chiselstrike.com/my-other-database-is-a-compile... ) and works well with Re
68.
by glommer 7y ago
That is one of the things that Nuvia is promising to change.
69.
by glommer 7y ago
You can't benchmark "server dominance". You can benchmark what you just described, plus piece other pieces of the puzzle together, like Nuvia Series-A, and then extrapolate from that. At the end it's still my opinion, I
70.
by glommer 7y ago
That comparison was never done. All CPU tests are on EBS backed instances, and in the end the I/O subsystem is compared in isolation for NVMe-backed instances in both cases.
71.
by glommer 7y ago
Agree that the advantage on storage is no ARM-specific. It is what it is on AWS and we have shown that. But the whole point is that the Arm platform is doing great. The CPU comparisons matter more
72.
by glommer 7y ago
They are not, they are all CPU-bound. Look at Figure4, that shows all CPUs at 100% utilization.
73.
by glommer 8y ago
Due to the way Cassandra and Scylla works, the SSTables contain a specific token range and each node is responsible for a part of the token range. sstable copying is possible, but the two clusters must have the exact same topology, with the
74.
by glommer 8y ago
More about Ultrabug's use case from Mongo in his awesome presentation at our summit: https://www.scylladb.com/tech-talk/numberly-on-joining-billi...
75.
by glommer 8y ago
Most of our users automate it. When you register, you are given access to the repository file for your preferred distribution. Once you have the repo, you can just apt-get it into every one of your nodes. Also Scylla provides non-gated acce
76.
by glommer 8y ago
And here it is: https://www.scylladb.com/2018/04/19/scylla-i-o-scheduler-3/
77.
by glommer 8y ago
Such an interesting timing! Just yesterday we have finished a redesign of this addressing some room-for-improvement areas that we saw after those two years. And I was about to start writing an article about it right now! Link soon =)
78.
by glommer 9y ago
Even if that is a problem, we provide anyone that is interested with a 30-day evaluation license of Scylla Enterprise.
79.
by glommer 9y ago
It does, but there are conditions that apply. Some companies don't like going that route - which in my opinion is not a thing, but I can't understand the concern. But for testing, I don't see any impediment.
80.
by glommer 9y ago
(ScyllaDB employee here) I don't believe one would need a commercial license just to test a product in any way? They are not making that part of any product at that point, so no concerns here.
81.
by glommer 10y ago
update: we didn't move forward with that implementation. Secondary indexes will be implemented on top of Materialized Views. Patches for Materialized Views already exist, and are soon to appear in preview releases.
82.
by glommer 10y ago
Every system has a maximum capacity, and after that is reached, the requests just see increased latency without increased throughput. At this point you scale up (by replacing it with better hardware) or out (by adding more nodes).
83.
Designing the Scylla Userspace Disk I/O Scheduler (Part 2)(scylladb.com)
6 points by glommer 10y ago|0 comments
84.
by glommer 10y ago
This feature was never described as half-ready. The ticket said we had half ready code, but it's part of the design process to choose whether or not we'll use that code. I can see, however, how this may give a reader the wrong imp
85.
by glommer 10y ago
There is nothing Cloud-specific in Scylla, though. Scylla will also target low latencies, and we have been very successful at that. But we also commit to supporting the Cassandra data model, so we won't really chase extra latencies if
86.
by glommer 10y ago
We are starting developing our solution for secondary index right now. We haven't yet made a decision regarding how we'll implement it.
87.
by glommer 10y ago
If you do run your own benchmarks, please publish them - together with your methodology. We fully stand behind our claims, and don't want to be seen as the "oh, it's the vendor saying, of course it's good". If you d
88.
by glommer 10y ago
Supporting the gossip protocol is hard, but so is supporting everything else. A more interesting question here is: if there is a bug in the gossip protocol, Cassandra side, and the addition of a different implementation of the same protocol
89.
by glommer 10y ago
We don't support mixed clusters, though, and are unlikely to do so. Most people testing Scylla at this point are doing A/B testing, using some proxy to replicate the writes to both clusters and then comparing the two.
90.
by glommer 10y ago
There are other things that the I/O setup script will do as well, like making sure your filesystem can handle async I/O properly and is fully patched, etc. It is indeed designed to be run everytime anything major changes in your d

More ›