3 ms·

THe default for debian 9 was 100% of ram. I have 64 gigs, so it was a bit much (especially as I only have 128 of disk.) The only time I've ever seen my[1] swa

THe default for debian 9 was 100% of ram. I have 64 gigs, so it was a bit much (especially as I only have 128 of disk.) The only time I've ever seen my[1] swap go above 500 megs was when I was running qterminal with a memory leak. It was a long running terminal, with a long running process that was extra ordinarily chatty. 4 gigs is probably enough for most people under most conditions. [1] this is workstations. on servers, I've seen it happen all the time. Crucially it gives one time to react.

cosarara 7y ago
You mention time to react. How do you get notified that memory usage is getting out of hand before the system is actually unusable?
- KaiserPro 7y ago
  Depends on the service its running really. I'd assume that you'd have key metrics plotted in grafana, so its case of following up/alerting on that In previous cases, It was fairly simple, an alert was fired because the queue size ballooned. Looking at the machine stats we saw that all the ram cache had been ejected just at the same time performance started to drop. Either way, its pretty trivial to put an alert on a stat in grafana. however, your mileage may vary.
nicolaslem 7y ago
I just did a fresh install of Debian 10 and it is still the default. I understand that they want to support hibernation out of the box but it creates gigantic swaps for a feature that I believe is rarely used, nowadays sleep is good enough and reboots are super fast. It would be great if the installer optionally asked how much swap to allocate without having to do the full partitioning manually.
parliament32 7y ago
Interestingly enough the debian installer freaks the fuck out if you have more ram than disk and choose the auto-partition option. We've run into this a few times with servers that have 512gb ram and a 120gb ssd installed. The installer doesn't seem to recognize this and try to set some sort of sane swap amount, instead it gives you some cryptic error messages about a bad disk and hangs.

cosarara 7y ago

You mention time to react. How do you get notified that memory usage is getting out of hand before the system is actually unusable?

KaiserPro 7y ago
Depends on the service its running really. I'd assume that you'd have key metrics plotted in grafana, so its case of following up/alerting on that In previous cases, It was fairly simple, an alert was fired because the queue size ballooned. Looking at the machine stats we saw that all the ram cache had been ejected just at the same time performance started to drop. Either way, its pretty trivial to put an alert on a stat in grafana. however, your mileage may vary.

nicolaslem 7y ago

I just did a fresh install of Debian 10 and it is still the default. I understand that they want to support hibernation out of the box but it creates gigantic swaps for a feature that I believe is rarely used, nowadays sleep is good enough and reboots are super fast. It would be great if the installer optionally asked how much swap to allocate without having to do the full partitioning manually.

parliament32 7y ago

Interestingly enough the debian installer freaks the fuck out if you have more ram than disk and choose the auto-partition option. We've run into this a few times with servers that have 512gb ram and a 120gb ssd installed. The installer doesn't seem to recognize this and try to set some sort of sane swap amount, instead it gives you some cryptic error messages about a bad disk and hangs.