Skip to contentSkip to conversation

About swapaccount=

DISCUSSION Jonas Schäfer 2 participants 3 messages Mar 2, 2023 – Mar 3, 2023 Memory management

lore
Share & tools
lore
#0 lore raw

Hi there,

By coincidence, I found this log message in my kernel logs:

Mär 02 17:23:19 sinistra kernel: The swapaccount= commandline option is deprecated. Please report your usecase to [email protected] if you depend on this functionality.

My usecase does depend on this in the following way:

I use LXC extensively to isolate workloads from one another. Kind of like docker, but with full operating systems inside.

Before I found out about swapaccount, I often ran into the issue that one misbehaving workload from one of those containers would bring the entire machine to a halt because it occupied lots of swap, and thus triggered significant slowdown.

With swapaccount, I limit swap to about 10% of the RAM assigned to the containers. This allows them to swap out unused stuff, but invokes the OOM killer before any significant slowdown happens.

The alternative would be to turn off swap for the system entirely, but it is running fairly efficiently thanks to swapping stuff out.

I'd be interested to hear about alternatives.

Thanks for hearing me, anyway.

kind regards,
Jonas Schäfer

#1 lore raw
Quoted 23 lines · Jonas Schäfer

Hi there,

By coincidence, I found this log message in my kernel logs:

Mär 02 17:23:19 sinistra kernel: The swapaccount= commandline option is deprecated. Please report your usecase to [email protected] if you depend on this functionality.

My usecase does depend on this in the following way:

I use LXC extensively to isolate workloads from one another. Kind of like docker, but with full operating systems inside.

Before I found out about swapaccount, I often ran into the issue that one misbehaving workload from one of those containers would bring the entire machine to a halt because it occupied lots of swap, and thus triggered significant slowdown.

With swapaccount, I limit swap to about 10% of the RAM assigned to the containers. This allows them to swap out unused stuff, but invokes the OOM killer before any significant slowdown happens.

Quoted 6 lines

The alternative would be to turn off swap for the system entirely, but it is running fairly efficiently thanks to swapping stuff out.

I'd be interested to hear about alternatives.

Thanks for hearing me, anyway.

If I understand correctly you were setting swapaccount=1, right?

IIRC, swapaccount= was deprecated in the sense that it is always on now (i.e you cannot set swapaccount=0).

Quoted 3 lines

kind regards,
Jonas Schäfer

#2 lore raw

Hi Yosry,

Quoted 26 lines · On Donnerstag, 2. März 2023 20:12:43 CET Yosry Ahmed wrote:
Quoted 25 lines · Jonas Schäfer

Hi there,

By coincidence, I found this log message in my kernel logs:

Mär 02 17:23:19 sinistra kernel: The swapaccount= commandline option is deprecated. Please report your usecase to [email protected] if you depend on this functionality.

My usecase does depend on this in the following way:

I use LXC extensively to isolate workloads from one another. Kind of like docker, but with full operating systems inside.

Before I found out about swapaccount, I often ran into the issue that one misbehaving workload from one of those containers would bring the entire machine to a halt because it occupied lots of swap, and thus triggered significant slowdown.

With swapaccount, I limit swap to about 10% of the RAM assigned to the containers. This allows them to swap out unused stuff, but invokes the OOM killer before any significant slowdown happens.

The alternative would be to turn off swap for the system entirely, but it is running fairly efficiently thanks to swapping stuff out.

Quoted 8 lines
Quoted 3 lines

I'd be interested to hear about alternatives.

Thanks for hearing me, anyway.

If I understand correctly you were setting swapaccount=1, right?

IIRC, swapaccount= was deprecated in the sense that it is always on now (i.e you cannot set swapaccount=0).

Thank you for the swift reply. Indeed, I am using swapaccount=1, so I assumed the deprecation warning was related to =1. If =1 continues to work as default, that just means I have one less thing to carry around in the grub config and is not a problem at all!

Thanks!

kind regards,
Jonas