Hadn't heard of Fabworks until today. Testing out a quote on some parts I was looking at getting from OSH Cut, they're actually much better on pricing _and_ have more capabilities. (!)
Have you used them a lot? Curious what your experience with them is if you're willing to share.
If it's all sheet metal-esque pieces, where you could suffice with just laser cut features and/or simple bends.. then you should take a look at OSH Cut.
They have a fairly powerful platform -- instant quoting from uploaded design files, 2D/3D views, DFM feedback, good turnaround times, etc -- and the pricing isn't half bad for prototyping... but might not be as good for large-scale runs compared to bigger shops where you can nail down volume pricing discounts.
Regarding safety, do you have any links around the test results for the Kioma, or other car seats? You've mentioned a lot about the safety scores/test results in comparison to other car seats, but I couldn't seem to find a single mention of that stuff on the website? I also tried to see if something like Consumer Reports had a review of a Kioma car seat (either the current one or the carbon fiber one) but they had nothing.
It feels more than a little bit coincidental to call it Noria when https://github.com/mit-pdos/noria exists (and has been posted about here on HN)... especially with the whole bit about incrementally computing changes.
One crucial difference I was able to spot is that Demikernel seems to have an approach that can work for OSes other than Linux. To wit, examples of the performance of the Demikernel approach are shown on a Windows system running in Azure.
Of the three examples you listed, none of them seem to support their kernel bypass capabilities in anything other than Linux.
Consistently reneging on bookings, though, is a strong signal, coupled with reports of discrimination. It's much easier to brush off before hand.. "oh, our plans actually changed, so we can accommodate you.
(granted, this can still happen, legitimately, even in a post-booking display mode.. but post-booking cancellations could be a signal for flakiness and, overall, a reason to put hosts on notice that they need to shape up)
The key is that the request rate be independent of the latency of individual requests.
In the case of wrk (the original wrk, not Gil Tene's version), you could use this version to check for maximum RPS / bandwidth. This is because it's sending requests as fast as it can, but one after the other.
In the case of wrk2, Gil Tene's version, you have to specify the rate at which to send requests. This is how it avoids coordinated omission.
As a small follow-on, there is also Barrage [1], which is more of a framework than anything else. kellabyte wrote it to benchmark changes to Haywire [2], so it's geared towards configuring your client and server, and then collecting all of the metrics from both the client side, and the server side, and displaying them in an easy-to-digest format.
This obviously isn't terribly useful if you're just trying to gauge request rates, or apply load, but it's very useful if you need a repeatable way to not only measure request rates but see how your server is doing under load.
Have you used them a lot? Curious what your experience with them is if you're willing to share.