ericvolp12

7 ms·

1.
by ericvolp12 1y ago
The article doesn't really do this justice, it's not really "opting to leave" it's that entire divisions inside the Science side of NASA have had their projects defunded and so all the work the people in those labs
2.
by ericvolp12 1y ago
The Y-axis in that graph is fucking hilarious
3.
by ericvolp12 1y ago
> Make it easy to do the right thing and hard to do the wrong thing. This is basically the mantra of every platform team I've worked on. Your goal is to make the easy and obvious solution to engineers' problems the "right&
4.
Attacking My Landlord's Boiler(blog.videah.net)
388 points by ericvolp12 1y ago|224 comments
5.
by ericvolp12 2y ago
This is probably what we'll end up with in the long-run. Things have been fast enough without it (aside from this issue) but there's a lot of low-hanging fruit for Timelines architecture updates. We're spread pretty thin from
6.
by ericvolp12 2y ago
Give Jetstream a try instead, it's all JSON for you already: websocat wss://jetstream2.us-west.bsky.network/subscribe
7.
by ericvolp12 2y ago
Oh that's pretty neat. Did you just end up being okay with large partitions? I've been really afraid to let partition sizes grow beyond 100k rows even if the rows themselves are tiny but I'm not really sure how much of a real
8.
by ericvolp12 2y ago
Interesting, we've got to 5M+ reads/sec in realistic simulated benchmarks and ~2M reads/sec of real-world-throughput on our clusters that are <10 nodes (though really high density). I don't think I've pushed writ
9.
by ericvolp12 2y ago
Did you guys end up redesigning the partitioning scheme to fit within Scylla's recommended partition sizes? I assume the tombstone issue didn't disappear with a move to Scylla but incremental compaction and/or SCTS might have
10.
by ericvolp12 2y ago
ScyllaDB scales horizontally on a shard-per-core architecture with a ballpark throughput of 12,500 Reads and 12,500 Writes per second per shard. If you're running Scylla across a total of 64 cores (maybe on 4 VMs with 16 vCPUs each), y
11.
by ericvolp12 2y ago
The funny part is ScyllaDB still uses tombstones for deletions, though they do have configurable compaction strategies and iirc Discord uses Scylla's Incremental Compaction Strategy that I suppose solves the specific issue they were de
12.
by ericvolp12 2y ago
Yeah exactly! The longer we can make it without having to shard the firehose, the better. It's a lot less complex to consume as a single stream.
13.
by ericvolp12 2y ago
The current relay firehose has more than 250 subscribers. It's served more than 8.5Gbps in real-world peak traffic sustained for ~12 hours a day. That being said, Jetstream is a lot more friendly for devs to get started with consuming
14.
by ericvolp12 2y ago
Yes the actual record content on the network isn't huge at the moment but the firehose doesn't include blobs (images and videos) which take up significantly more space. Either way, yeah it's pretty lightweight. Total number o
15.
by ericvolp12 2y ago
The 10x surge in traffic was us gaining 3.5M new users over the course of a week (growing the entire userbase by >33%) and all these users have been incredibly active on a daily basis. Lots of these numbers are public and the impact of t
16.
by ericvolp12 2y ago
It's impossible to use the compressed version of the stream without using a client that has the baked-in ZSTD dictionary. This is a usability issue for folks using languages without a Jetstream client who just want to consume the webso
17.
by ericvolp12 2y ago
Jetstream isn't an official change to the Protocol, it's an optimization I made for my own services that I realized a lot of other devs would appreciate. The major driving force behind it was both the bandwidth savings but also ma
18.
by ericvolp12 2y ago
The full Firehose provides two major verification features. First it includes a signature that can be validated letting you know the updates are signed by the repo owner. Second, by providing the MST proof, it makes it hard or impossible fo
19.
An Entire Social Network in 1.6GB (GraphD Part 2)(jazco.dev)
1 points by ericvolp12 2y ago|0 comments
20.
SREs Solve Problems at Home (Making My Dumb Fridge Smart)(blog.ericv.me)
1 points by ericvolp12 6y ago|0 comments
21.
by ericvolp12 6y ago
This was really well explained and interesting. Funnily enough I'm pretty sure this is a really similar method to urinal design, so if this whole basketball thing doesn't work out for ya, you could always work for American Standar
22.
by ericvolp12 7y ago
Mullvad already supports linux wireguard clients if you want to just cut out the firefox middleman and use it internationally too - https://mullvad.net/en/download/#linux
23.
by ericvolp12 7y ago
Obligatory - https://www.youtube.com/watch?v=Z7iSbrkeAhE (LTT Review) Take it however you want to, as a joke or as serious criticism.