jeffinhat

6 ms·

1.
by jeffinhat 11mo ago
Awesome, I will! It would be great to see where the limits are with this approach. I think at some point, you need to go deeper into the apiserver for scale than an API compatible shim, but this is just conjecture and not real data.
2.
by jeffinhat 11mo ago
This is an awesome experiment and write up. I really appreciate the reproducibility. I would like to see how moving to database that scales write throughput with replicas would behave, namely FoundationDB. I think this will require more tha
3.
by jeffinhat 1y ago
It's definitely a different use case but given they haven't had to tap into their follower replicas for scale, it must be pretty efficient and lightweight. I suspect not having ACLs helps. They also cite a minimum 2MB size, so not
4.
by jeffinhat 2y ago
They are developing this simulation concept as a platform: https://antithesis.com/
5.
by jeffinhat 4y ago
See also- Snap: a Microkernel Approach to Host Networking: https://research.google/pubs/pub48630/
6.
by jeffinhat 5y ago
I haven't experimented with it yet, but I expect that over TCP things degrade more gracefully. It seems earlier iterations of storage over networking didn't want to pay the overhead of TCP and lost out on the general purpose benef
7.
by jeffinhat 5y ago
It certainly isn't faster or more reliable for a single node, but this is just homelab stuff. Nothing in mine is particularly necessary. I think it's interesting because it's now accessible and receiving support from multiple
8.
by jeffinhat 5y ago
I've been messing with NVMe over TCP at home lately and it's pretty awesome. You can scoop up the last-gen of 10GBe/40GBe networking on eBay for cheap and build your own fast disaggregated storage on upstream Linux. The kerne
9.
by jeffinhat 9y ago
This is awesome. I've been trying to reach for go instead of bash more and more and this is exactly what I need for the small stuff. Any ideas how it could relate to the go toolchain? could I stick my Neugram files in a repo and go get
10.
by jeffinhat 9y ago
The value of the Makefile is for automating repetitive dev tasks. Consumers of a golang CLI should use `go get` but this makes it easier for contributors who run tests, cut releases, .. The authors example is clean/simple. Here's
11.
Kubo: Kubernetes on Cloud Foundry Powered by BOSH(pivotal.io)
10 points by jeffinhat 10y ago|1 comments
12.
by jeffinhat 10y ago
noexcept is a messier than const because it's not straightforward to assess if code you rely on should be throwing or not since that's an implementation detail versus a contract around data ownership. This makes maintenance hard a
13.
by jeffinhat 10y ago
A lot of large C++ shops re-implement much of the standard library, often to add niche features that don't make sense as a standard. I believe replacing the allocator in a lot of the standard data structures to a non-throwing one will
14.
by jeffinhat 11y ago
Was the connector not an option for you or have things gotten better? I commute in slightly off hours (7am and 4pm) and it consistently takes ~35 minutes door to door.
15.
by jeffinhat 11y ago
Seems interesting! It would be nice to have a diff between the base version and patch-ready version of the various software (eg, redis). It's hard to quickly understand what the integration of this into an large, existing piece of soft
16.
Inside the Azure Storage Outage of November 18th(channel9.msdn.com)
1 points by jeffinhat 12y ago|0 comments