All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Did push-ups break a Ryzen? (Nexril Dallas)
Dallas was one of initial locations on my push-ups delivery network.
Today it went offline:
Hello push-up specialist,
We are currently investigating a potential hardware issue with one of our VPS nodes (RYZEN01DAL) that has caused this node to crash and reboot several times this morning.
Customers with servers on this node may notice some downtime in the process. We will try to keep this as short as possible and have everyone back online soon.
Best Regards,
Nexril
According to UptimeRobot, the server has been restarted more than 3 times in the past 4 hours.
The incident is still ongoing.
Given how many push-ups are served from this server, I guess the sheer amount of push-ups has broken the Ryzen.
If you are watching push-up videos from me, my brother, and other contributors, you would experience higher latency and lower resolution because of this.
We apologize for the inconvenience.
Comments
Have your push-ups video backed up. The end is nigh.
to much bending on the motherboard, because one guy needed to show off by doing the pushups with one hand instead of 2.
The push-ups did indeed break the Ryzen.
Temporary server has a different CPU model:
We weren't the only one to do a mobo replacement to bring in the New Year.
https://portal.incognet.io/serverstatus.php?view=resolved
Also Ryzen.
Node was rebooting as quickly as every other minute.
The push-ups repository has two replicas, currently in Nexril Dallas and Evolution Host Roubaix.
If I lose a repository node, there would be no data loss.
If I lose both, videos are unavailable.
The push-ups delivery network is completely distributed.
If I lose one node, there would be no service interruption.
If I lose two nodes causing a network partition, videos are unavailable in certain regions.
I hope not.
I paid 24 push-ups as setup fee for this server.
Not caused by my push-ups.
I have store credit but haven't ordered anything yet.
Blame @Boogeyman and the Nigh Sect.
Time to go from push-ups to pull-ups.
That's a crunch, not a push-up.
Crunch is a core exercise.
Push-up is a chest and tricep exercise.
Planet Fitness #UnitedWeMove campaign in 2020 was full of crunches.
The sheer amount of push-ups burnt the Ryzen, not the motherboard.
I don't have the strength to do push-ups with one hand.
If you can, please contribute a video.
Open bobs @yoursunny
Pushups + Constipation = Reverse Log Ryzen Gang
Why the fuck does latency matter so much for one way video streaming? It's just eaten up in the upfront buffering, which nobody will notice 50ms vs 150ms. It certainly doesn't make sense that the resolution would be lower unless the bandwidth was lower (which is a function of latency, but not a hard limit). Are you doing it wrong?
Named Data Networking protocol requires the consumer (data receiver, which is the browser in my app) to send one request for each segment (8KB).
This property is called flow balance and it allows the consumer to perform congestion control.
(TCP has a similar mechanism using ACK packets, but congestion control algorithm runs on the sender side)
The congestion control algorithm is still being designed and improved.
I'm currently using CUBIC, but it's not working well with in-network caching.
In particular, if some segments are cached and some are not, the bandwidth estimation from CUBIC algorithm would fluctuate, and then Shaka Player goes crazy.
Researchers in UCLA are investigating a BBR-inspired congestion control algorithm, that supposedly is compatible with in-network caching.
I'm still reading their paper to understand how it works.
I expect some improvements after that.
Sounds like your buffers are too small.
Which buffer are you referring to?
How did you infer the buffers are too small?
Here is accurate description of the buffer:
https://www.urbandictionary.com/author.php?author=Rob Ta
We get 2 month service time extension for a few hours of downtime and no data loss?
Not acceptable!
Video buffer on client side if it's the one asking for video. Give it more runway.