Defcon: Preventing overload with graceful feature degradation (2023)
1–10 of 107 posts
Re: Defcon: Preventing overload with graceful feature degradation (2023)
#2Re: Defcon: Preventing overload with graceful feature degradation (2023)
#3Am I reading the second figure right? Facebook can do 130*10^6 queries/second == 130,000,000 queries/second?!
Re: Defcon: Preventing overload with graceful feature degradation (2023)
#4Am I reading the second figure right? Facebook can do 130*10^6 queries/second == 130,000,000 queries/second?!
Re: Defcon: Preventing overload with graceful feature degradation (2023)
#5Am I reading the second figure right? Facebook can do 130*10^6 queries/second == 130,000,000 queries/second?!
Re: Defcon: Preventing overload with graceful feature degradation (2023)
#6Am I reading the second figure right? Facebook can do 130*10^6 queries/second == 130,000,000 queries/second?!
Re: Defcon: Preventing overload with graceful feature degradation (2023)
#7Am I reading the second figure right? Facebook can do 130*10^6 queries/second == 130,000,000 queries/second?!
Re: Defcon: Preventing overload with graceful feature degradation (2023)
#8Re: Defcon: Preventing overload with graceful feature degradation (2023)
#9Am I reading the second figure right? Facebook can do 130*10^6 queries/second == 130,000,000 queries/second?!
Re: Defcon: Preventing overload with graceful feature degradation (2023)
#10For example, as soon as I log in I see a bell icon in the upper right with a bright red circle containing an exact positive integer number of notifications. It practically screams “click here, you have urgent business”.
I can then leave the web page sitting there for any number of minutes, and no matter how long I wait, if I click on that notification icon it will take a good 20 seconds to load the list of new notifications. (This is on gigabit fiber in a major metro area, so not a plumbing issue.)