Lightnews — Scholar-powered news

Reposted by Shivansh Vij

Damon Cortesi @dacort.velocipig.com · 4d

🙋‍♂️

kccncna2025.sched.com/event/27Fd6/...

2 2

Shivansh Vij @shivanshvij.com · 4d

Who is coming to KubeCon NA 2025 in Atlanta?

2 2

Shivansh Vij @shivanshvij.com · Apr 29

Marked your account for priority!

2

Shivansh Vij @shivanshvij.com · Apr 29

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!

1 4

Shivansh Vij @shivanshvij.com · Apr 13

RWX looks amazing! I wonder if there’s an opportunity for collaboration there…

2

Shivansh Vij @shivanshvij.com · Mar 4

I can’t wait to open source our filesystem this month, it’s ridiculous the kind of stuff we jammed into the Linux kernel

3

Reposted by Shivansh Vij

Chris @chris.blue · Mar 3

I'm getting more and more excited about drop-in, frictionless infrastructure. Lots going on in observability, containers, cloud compute, etc. eBPF is part of it, so is monkey patching. Some interesting ones: @loopholelabs.io, @polarsignals.com, junctionlabs.io ﹩, subtrace.dev ﹩

3 2 26

Shivansh Vij @shivanshvij.com · Feb 18

- 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

3

Shivansh Vij @shivanshvij.com · Feb 18

Request: Topics for the @loopholelabs.io Blog

I want to start posting some short-form blogs that go through the technical challenges of building @loopholelabs.io and how we’ve solved them.

If folks have requests for content they’d like covered now’s the time to ask!

Topics I have so far 👇

1 2 4

Reposted by Shivansh Vij

Trezy @trezy.codes · Jan 19

Just got to Malta for the company getaway! It’s really convenient that these EU outlets have a whole THREE USB-C outlets! So great.

3 1 24

Shivansh Vij @shivanshvij.com · Jan 14

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.

BOINCCompute for Science

BOINC is an open-source software platform for computing using volunteered resources

boinc.berkeley.edu

Shivansh Vij @shivanshvij.com · Jan 10

Donate to BOINC!

1

Shivansh Vij @shivanshvij.com · Jan 1

Yessir - the price to performance ratio alone makes them exciting but once you factor in power draw it becomes a no-brainer

1

Shivansh Vij @shivanshvij.com · Jan 1

If Asahi Linux ends up supporting M4 chips this year, I think adoption in datacenters will go through the roof

1 3

Reposted by Shivansh Vij

Shivansh Vij @shivanshvij.com · Dec 27

I think the most excited thing about this blog post is the one we get to publish next - a deep dive into how Architect works under the hood.

There were so many “impossible” problems we had to solve to make Architect a reality - and now that we have I’m having a blast explaining how we did it.

Loophole Labs @loopholelabs.io · Dec 27

New blog post!

Run any application on Spot Instances with zero downtime and 75%+ cost savings - and no code changes required.

Architect eliminates the reliability concerns that previously made Spot Instances impractical for production workloads.

⬇️ Link in comments ⬇️

3 3 8

Shivansh Vij @shivanshvij.com · Dec 27

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

1 1

Shivansh Vij @shivanshvij.com · Dec 27

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.

1 1

Shivansh Vij @shivanshvij.com · Dec 27

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.

1

Shivansh Vij @shivanshvij.com · Dec 27

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

1

Reposted by Shivansh Vij

James Bayer @jambay.bsky.social · Dec 27

@evanphx.dev this looks pretty cool loopholelabs.io/blog/rethink... built on OSS live migration tech that forked firecracker and related virtualization technology github.com/loopholelabs...

Rethinking Spot Instances - How We Solved the Preemption Problem

Run any application on Spot Instances with zero downtime and 75%+ cost savings - no code changes required. Architect eliminates the reliability concerns that previously made Spot Instances impractical...

loopholelabs.io

1 3 7

Shivansh Vij @shivanshvij.com · Dec 27

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

1 2

Reposted by Shivansh Vij

James Bayer @jambay.bsky.social · Dec 27

This looks super cool. Get up to 75% cost-savings of using spot instances without data loss or interruption. My mental model of what this does is the equivalent of vSphere vMotion, but for spot instance workloads running in the Cloud.

Shivansh Vij @shivanshvij.com · Dec 27

I think the most excited thing about this blog post is the one we get to publish next - a deep dive into how Architect works under the hood.

There were so many “impossible” problems we had to solve to make Architect a reality - and now that we have I’m having a blast explaining how we did it.

Loophole Labs @loopholelabs.io · Dec 27

New blog post!

Run any application on Spot Instances with zero downtime and 75%+ cost savings - and no code changes required.

Architect eliminates the reliability concerns that previously made Spot Instances impractical for production workloads.

⬇️ Link in comments ⬇️

1 1 4

Shivansh Vij @shivanshvij.com · Dec 27

I think the most excited thing about this blog post is the one we get to publish next - a deep dive into how Architect works under the hood.

There were so many “impossible” problems we had to solve to make Architect a reality - and now that we have I’m having a blast explaining how we did it.

Loophole Labs @loopholelabs.io · Dec 27

New blog post!

Run any application on Spot Instances with zero downtime and 75%+ cost savings - and no code changes required.

Architect eliminates the reliability concerns that previously made Spot Instances impractical for production workloads.

⬇️ Link in comments ⬇️

3 3 8

Reposted by Shivansh Vij

Loophole Labs @loopholelabs.io · Dec 27

Want to see it in action? Read the post here:
loopholelabs.io/blog/rethink...

Rethinking Spot Instances - How We Solved the Preemption Problem

Run any application on Spot Instances with zero downtime and 75%+ cost savings - no code changes required. Architect eliminates the reliability concerns that previously made Spot Instances impractical...

loopholelabs.io

1 1 3

Reposted by Shivansh Vij

Loophole Labs @loopholelabs.io · Dec 27

New blog post!

Run any application on Spot Instances with zero downtime and 75%+ cost savings - and no code changes required.

Architect eliminates the reliability concerns that previously made Spot Instances impractical for production workloads.

⬇️ Link in comments ⬇️

1 3 12