Talk:Improving performance

From ArchWiki


Is this section still accurate?

"The package zramswapAUR provides an automated script for setting up such swap devices with optimal settings for your system (such as RAM size and CPU core number). The script creates one zram device per CPU core with a total space equivalent to the RAM available, so you will have a compressed swap with higher priority than regular swap, which will utilize multiple CPU cores for compressing data."

According to the Linux Kernel docs [1] "ZRAM will always allocate multiple compression streams - one per online CPUs - thus allowing several concurrent compression operations". On the gentoo wiki making multiple devices to get scaling is mentioned as a workaround for pre 3.15 kernels.

—This unsigned comment is by Smasher816 (talk) 00:08, 10 October 2017‎. Please sign your posts with ~~~~!

Close. Related section is already updated. --Fengchao (talk) 10:25, 31 October 2022 (UTC)

Improving system responsiveness under low-memory conditions >> cgroups-v2

Enabling the "memory" controller in cgroups-v2 and setting "memory.min=268435456" also helps. Can someone adapt this information for Archlinux? Tsester (talk) 19:38, 28 October 2020 (UTC)

Do you have any supporting reference about this. Setting this value will protect usused memory from reclaimed, so it may make responsiveness worse. -- Fengchao (talk) 00:53, 1 November 2022 (UTC)

some way improve performance

Sorr, I'm working on translation of User:Dragonwater/Improving_performance_(简体中文)_tmp,, may have not time to add this things:

Anyone has time to do this?

All codes are:

systemctl enable dbus-broker.service
systemctl --global enable dbus-broker.service

Then reboot.

systemctl enable --now uresourced

Dragonwater (talk) 11:33, 4 June 2021 (UTC)