seppel
Joined 9 years ago
Joined 9 years ago
When they show an advertisement of, say, some asian company to a russian user, they are still making money, aren't they?
But it has to be GB to actually make a difference. If your swap is not full of GB of data, then obviously you don't need it (or it just becomes a reserve when you are in an OOM situation - but this is where you don't want to be with swap avaible either)
Then you obviously have a workload where having swap make sense (and you could even add swap on the fly in such a case). But that is not typical at all.
Yes, but the author is most likely optimizing for a metric that I don't care so much in my per personal computer while dismissing metrics that I care about.
> It was always the case. but then a TB of disk isn't that expensive anymore.
But swapping out GB of RAM is expensive in terms of latency.
This is true, but it still takes time. What kind of workload do you have where you swap out 32GB of RAM? If you are in this situation you almost certainly need to buy these additional 32GB of RAM.
And I have time to think about better problems than "You can achieve better swap behaviour under memory pressure and prevent thrashing by utilising memory.low and friends in cgroup v2."
The core problem with swap is that nowadays you need gigabytes of swap to actually make a difference (when you have 32GB of RAM, 1GB of swap is 1/32 of a difference). And you certainly don't want to system to swap in and out gigabytes of memory.
And this caused a lot of extra trouble on top of the incident.
Well, in principle, the frontend just has to distinguish between HTTP status 500 (something broken in the backend, not the fault of the user) and some HTTP status code 4xx (the user did something wrong).
Then these transactions will be delayed anyway. You could still process 99.99% of the transactions on Sunday.
Visa, Mastercard, Paypal as operate 24/7. ATMs operate 24/7. Neo banks allow intra-bank transfers 24/7. And they deal with the fraud and AML stuff.