Have you noticed something more promising ? I am not sure, because I typically do not eat carbs.
Long fat pipe sees dramatic throughput drops with tcp and relatively small packet loss. Possibly we were holding it wrong; would love to know if there is some definitive guide to doing it right. Good success with UDT.
I would think of UDP with redundant encoding / FEC, to avoid retransmits.
How did that happened? Seems multicast is already built in, just use that for massive broadcast. Is TCP used just so we can get an ACK that it is received. Seems multicast and UDP shouldn't be a problem if we just want massive people to listen in on it, but if we want to also track these people then that is another story.
From a user perspective, use UDP/multicast all the way. Let the client to request something if it is dropped or missing or otherwise just multicast for everything.
Aeron latency histograms vs TCP are quite nice in the same DC on enterprise-grade networking hardware. But it really makes sense to use if a single-digit or low-double digit microsecond latency improvement on P50 is worth the effort. Or if the long tail with TCP is a dealbreaker, as Aeron has much nicer P99+ regardless of how well optimized a TCP setup is. Also, if one can leverage multicast that's nice, but not only clouds have it disabled, and Aeron works fine with unicast to N.
However, there are gotchas with threading and configuration overall. Cross-DC setup may surprise in a bad way if buffers are not configured to account for bandwidth-delay product. Any packet loss on high-latency network leads to a nasty NACK storm that is slow to recover under load. It's better to set the highest QoS and ensure the network is never dropping packets, e.g. calculate the real peak instant load vs hardware capacity. Relative latency savings cross-DC become less interesting the longer the distance, so there's nothing wrong with TCP there. Another note is that, e.g. ZMQ is slow not because of TCP but because of its internals, almost 2x slower for small packets than raw well-tuned TCP sockets, which are not that bad vs Aeron. Also, Aeron is not for sending big blobs around, the best is to use it with small payloads.
Aeron is designed with mechanical sympathy in mind by the guys who coined this term and have been evangelizing it for years, and it's visible. Lots to learn from the design & implementation (tons of resources on the web) even without using it in prod.
https://pmc.ncbi.nlm.nih.gov/articles/PMC7068624/
Conclusion Review shows that Novamin has significantly less clinical evidence to prove its effectiveness as a remineralization agent in treating both carious and non-carious lesion. Hence, better designed clinical trials should be carried out in the future before definitive recommendations can be made.
For Novamin alone, I've seen and understood the claims of sensitivity protection with hydroxyl-carbonate apatite (HCA). The paper explains it in 4.3. The layer is temporary and protects from acids, conserving the teeth tissue below.
But F is essential and my paste has it together with Novamin. It seems they may work well together. But the paper also explains that F works with saliva rich in minerals to repair the enamel. So if Novamin creates a strong layer, it may block access of F + saliva to enamel (my speculation, as in 4.2 they say "A clean tooth surface is required to access the mineral-deficient spot.").
So maybe a classical Ca+F paste is better overnight when no acid exposure is expected, but Novamin is nice in the morning before breakfast.