Marked your account for priority!
April 29, 2025 at 3:00 AM
Marked your account for priority!
We’re not just putting this together for CI, we’ll also be connecting it to a CLI so you can just throw your local environment into a cloud VM to run really quickly and be torn down!
April 29, 2025 at 2:26 AM
We’re not just putting this together for CI, we’ll also be connecting it to a CLI so you can just throw your local environment into a cloud VM to run really quickly and be torn down!
RWX looks amazing! I wonder if there’s an opportunity for collaboration there…
April 13, 2025 at 10:20 PM
RWX looks amazing! I wonder if there’s an opportunity for collaboration there…
I can’t wait to open source our filesystem this month, it’s ridiculous the kind of stuff we jammed into the Linux kernel
March 4, 2025 at 3:24 AM
I can’t wait to open source our filesystem this month, it’s ridiculous the kind of stuff we jammed into the Linux kernel
- How to run VMs anywhere (even without KVM support)
- How to do L3/4 Checksums in eBPF XDP hooks
- How to write an in-kernel filesystem (and why)
- Deduplicating memory between VMs
- Reverse Engineering the CUDA API
- How to do L3/4 Checksums in eBPF XDP hooks
- How to write an in-kernel filesystem (and why)
- Deduplicating memory between VMs
- Reverse Engineering the CUDA API
February 18, 2025 at 1:10 AM
- How to run VMs anywhere (even without KVM support)
- How to do L3/4 Checksums in eBPF XDP hooks
- How to write an in-kernel filesystem (and why)
- Deduplicating memory between VMs
- Reverse Engineering the CUDA API
- How to do L3/4 Checksums in eBPF XDP hooks
- How to write an in-kernel filesystem (and why)
- Deduplicating memory between VMs
- Reverse Engineering the CUDA API
boinc.berkeley.edu
You can volunteer your unused compute capacity towards research projects run by Berkeley For things like discovering pulsars, studying climate change, etc.
You can volunteer your unused compute capacity towards research projects run by Berkeley For things like discovering pulsars, studying climate change, etc.
BOINCCompute for Science
BOINC is an open-source software platform for computing using volunteered resources
boinc.berkeley.edu
January 14, 2025 at 12:49 AM
boinc.berkeley.edu
You can volunteer your unused compute capacity towards research projects run by Berkeley For things like discovering pulsars, studying climate change, etc.
You can volunteer your unused compute capacity towards research projects run by Berkeley For things like discovering pulsars, studying climate change, etc.
Yessir - the price to performance ratio alone makes them exciting but once you factor in power draw it becomes a no-brainer
January 1, 2025 at 9:48 PM
Yessir - the price to performance ratio alone makes them exciting but once you factor in power draw it becomes a no-brainer
Here’s a demo of us migrating between spot instances across cloud providers all of which have different CPUs (generations, clock speeds, etc.)
loophole.sh/kc2024
loophole.sh/kc2024
December 27, 2024 at 8:39 PM
Here’s a demo of us migrating between spot instances across cloud providers all of which have different CPUs (generations, clock speeds, etc.)
loophole.sh/kc2024
loophole.sh/kc2024
Yep - and in those situations we can swap to a different instance type silently. We prefer that over a different region.
One of the more “impossible” problems we had to solve was migrating between different cpu types/generations seamlessly - that’s going to be the highlight of the next post.
One of the more “impossible” problems we had to solve was migrating between different cpu types/generations seamlessly - that’s going to be the highlight of the next post.
December 27, 2024 at 8:37 PM
Yep - and in those situations we can swap to a different instance type silently. We prefer that over a different region.
One of the more “impossible” problems we had to solve was migrating between different cpu types/generations seamlessly - that’s going to be the highlight of the next post.
One of the more “impossible” problems we had to solve was migrating between different cpu types/generations seamlessly - that’s going to be the highlight of the next post.
So the nice thing about architect is that we can always fall back to on-demand instances if there’s no spot available - or we can switch to a different region, or if we’re really in a pinch we can swap to a completely different cloud provider.
Users can configure what level of fallback they want.
Users can configure what level of fallback they want.
December 27, 2024 at 8:35 PM
So the nice thing about architect is that we can always fall back to on-demand instances if there’s no spot available - or we can switch to a different region, or if we’re really in a pinch we can swap to a completely different cloud provider.
Users can configure what level of fallback they want.
Users can configure what level of fallback they want.
For sure - and we do recommend some level of overprovisioning to help against this, but because we run in your cloud account we generally only have to worry about the size of the individual customer’s workload on a per-region basis
December 27, 2024 at 8:34 PM
For sure - and we do recommend some level of overprovisioning to help against this, but because we run in your cloud account we generally only have to worry about the size of the individual customer’s workload on a per-region basis
Your mental model is spot on (no pun intended)- though to make it work across spot instances and even cloud providers we had to go far beyond the capabilities of vmotion
December 27, 2024 at 7:26 PM
Your mental model is spot on (no pun intended)- though to make it work across spot instances and even cloud providers we had to go far beyond the capabilities of vmotion