Not necessarily. In classic C we often build complex state machines to handle errors - especially when there are many things that need to be initialized (malloced) one after another and each might fail. Think the infamous "goto error".
I think defer{} can simplify these flows sometimes, so it can indeed be useful for good old style C.
Yes, works well with AMD. You can compile multi-target so that you'll have e.g. SSE4.2, AVX2, AVX512 support built to your binaries and the best (widest) version is picked by the runtime automatically.
It means every lawmaker isn’t a geologist. That’s fine. It also means there clearly wasn’t enough public input from geologists that someone would have noticed a name they’d never seen in a group they were familiar with.
I’ll go out on a limb and guess that none of the industry groups found this funny. They want to replicate this law in other states. The lawyers who worked on it, on the other hand, only work in North Dakota. And calling a spade a spade, I guess if I needed something in front of that legislature I’d at least know they’re competent and crafty.
My understanding: You are one legislator among many; you have almost no power on your own. To deliver results for your constituents or to accomplish anything depends especially on party leadership and on other members of your party prioritizing your wishes over many other things. If you don't follow leadership, if you aren't on the team, they won't do anything for you.
Silly curiosity - what's that "BEAM-appreciator" in that bio? I could only think of a protein brand name (that too not from my geography) shortened as BEAM :/
In summary, the location at which an IP egresses Cloudflare network has nothing to do with the geo-ip mapping of that IP. In some cases the decision on where to egress is optimised for "location closest to the user", but this is also not always true.
And then there is the Internet. Often some country (say Iran) egresses from a totally different place (like Frankfurt) due to geopolitics and just location of cables.
So, there is a dashboard internally for that. When we do ProbeNet PoP assessment, we have a high-level overview of the frequent and favored connections. We have a ton of servers in Africa, and there is a strong routing bias towards France, Germany, and the UK instead of neighboring connections.
Everyone in our engineering and leadership is very close with various CDN companies. We do echo this idea to them. It is not IP geolocation; we actually have a ton of routing data they can use.
> Coordinator sees Node A has significantly fewer rows (logical count) than the cluster average. It flags Node A as "underutilized."
Ok, so you are dealing with a classic - you measure A, but what matters is B. For "load" balancing a decent metric is, well, response time (and jitter).
For data partitioning - I guess number of rows is not the right metric? Change it to number*avg_size or something?
If you can't measure the thing directly, then take a look at stuff like "PID controller". This can be approach as a typical controller loop problem, although in 99% doing PID for software systems is an overkill.
The trouble with mmap is the performance cliff. A node goes from 'fine' to 'dead' almost instantly, which breaks our balancing logic.
You are right that we need better backpressure. Instead of a smarter coordinator, we probably need 'dumber' nodes that aggressively shed load (return 429s) the moment local pressure spikes, rather than waiting for a re-balance.
reply