@LukeYoungblood@gf_256 Not if they learn to host the models locally? And somehow find a way to pool they're resources and run powerful unquantized models?
NAT-based Load Balancers (LB) like HAProxy or Nginx are usually the default choice. But there is a problem with them: all replies go back through the LB, too. And while requests are often short, replies can be x10-100 times heavier.
That means more bandwidth on the LB, and the biggest traffic flowing through the one component you'd least like to bottleneck.
Direct Server Return (DSR) fixes that: requests go through the LB, responses don't.
Building an eBPF-based DSR load balancer is a great way to actually understand both eBPF and how DSR really works at L2. Check out Teodor Podobnik's most recent hands-on tutorial, where he step-by-step walks you through the process https://t.co/EGI03Qpn08
@tharun0x@theliverdoc@PrakashRaghav Thanks I was unable to get to their channel for some reason.
FWIW here is the associated FB page
https://t.co/rll8ZOHVpO
We just hired a new senior engineer. Starts next month.
His salary is $140K. That's $15K more than my current senior engineer who's been here for four years.
My current guy doesn't know this yet. But he will eventually. And when he finds out, he's going to be pissed.
Here's what I'm banking on: he'll come to me asking for a raise to match the new hire.
I'll act sympathetic. I'll say the market has changed, and yes, it's frustrating, but my hands are tied by HR compensation bands.
Then I'll offer him $10K more. He'll take it because it's better than nothing.
Net result: I keep a good engineer happy with less money than he could've gotten, and I look like I fought for him.
The new hire? He has no idea he could've probably gotten $150K if he'd negotiated harder.
I lowballed the offer and he accepted immediately.
So I'm paying two senior engineers a combined $25K less than market rate, and both of them think I'm on their side.
Salary management is just information asymmetry with better branding.