Search Results for 'swap'

[Forum Admin rokytnji]

On My Wacom Touchscreen Dell Latitude XT2 before I head out to the shop computer.

harry@biker:~
$ pinxi -zv7
System:
  Kernel: 5.10.0-18-amd64 arch: x86_64 bits: 64 compiler: gcc v: 10.2.1
    Desktop: Fluxbox v: 1.3.7 info: tint2 vt: 7 dm: LightDM v: 1.26.0
    Distro: MX-21.2.1_x64 Wildflower October 20  2021
    base: Debian GNU/Linux 11 (bullseye)
Machine:
  Type: Portable System: Dell product: Latitude XT2 v: N/A
    serial: <superuser required> Chassis: type: 8 serial: <superuser required>
  Mobo: Dell model: 0HJ48R serial: <superuser required> BIOS: Dell v: A01
    date: 05/07/2009
Battery:
  ID-1: BAT0 charge: 38.8 Wh (100.0%) condition: 38.8/42.2 Wh (91.9%)
    volts: 10.7 min: 11.1 model: Sanyo DELL H986H98 type: Li-ion
    serial: <filter> status: full
Memory:
  RAM: total: 4.77 GiB used: 1.25 GiB (26.2%)
  RAM Report:
    permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: dual core model: Intel Core2 Duo U9600 bits: 64 type: MCP
    smt: <unsupported> arch: Core Yorkfield rev: A cache: L1: 128 KiB L2: 3 MiB
  Speed (MHz): avg: 1004 high: 1062 min/max: 800/1601 boost: enabled cores:
    1: 1062 2: 947 bogomips: 6378
  Flags: acpi aperfmperf apic arch_perfmon bts clflush cmov constant_tsc
    cpuid cx16 cx8 de ds_cpl dtes64 dtherm dts est fpu fxsr ht ida lahf_lm lm
    mca mce mmx monitor msr mtrr nopl nx pae pat pbe pdcm pebs pge pni pse
    pse36 pti rep_good sep smx sse sse2 sse4_1 ssse3 syscall tm tm2 tsc vme
    xsave xtpr
Graphics:
  Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Dell
    driver: i915 v: kernel ports: active: LVDS-1
    empty: DP-1, DP-2, HDMI-A-1, SVIDEO-1, VGA-1 bus-ID: 00:02.0
    chip-ID: 8086:2a42 class-ID: 0300
  Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: intel gpu: i915
    display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1280x800 s-dpi: 96 s-size: 338x211mm (13.31x8.31")
    s-diag: 398mm (15.69")
  Monitor-1: LVDS-1 mapped: LVDS1 model: AU Optronics 0xa114 res: 1280x800
    hz: 60 dpi: 125 size: 261x163mm (10.28x6.42") diag: 308mm (12.1")
    modes: 1280x800
  OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express (CTG)
    v: 2.1 Mesa 20.3.5 direct render: Yes
Audio:
  Device-1: Intel 82801I HD Audio vendor: Dell driver: snd_hda_intel
    v: kernel bus-ID: 00:1b.0 chip-ID: 8086:293e class-ID: 0403
  Sound Server-1: ALSA v: k5.10.0-18-amd64 running: yes
  Sound Server-2: PulseAudio v: 14.2 running: yes
Network:
  Device-1: Intel 82567LM Gigabit Network vendor: Dell driver: e1000e
    v: kernel port: efe0 bus-ID: 00:19.0 chip-ID: 8086:10f5 class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Device-2: Intel WiFi Link 5100 driver: iwlwifi v: kernel pcie:
    speed: 2.5 GT/s lanes: 1 bus-ID: 0c:00.0 chip-ID: 8086:4232 class-ID: 0280
  IF: wlan0 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  WAN IP: <filter>
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB
    driver: btusb v: 0.8 bus-ID: 6-1:2 chip-ID: 0a12:0001 class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter>
    bt-v: 1.2 lmp-v: 2.0 sub-v: c5c hci-v: 2.0 rev: c5c
Logical:
  Message: No logical block device data found.
RAID:
  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
    v: 3.0 port: 6ea0 bus-ID: 00:1f.2 chip-ID: 8086:282a rev: N/A
    class-ID: 0104
Drives:
  Local Storage: total: 167.68 GiB used: 61.87 GiB (36.9%)
  ID-1: /dev/sda vendor: OCZ model: D2CSTK181M11-0180 size: 167.68 GiB
    speed: 3.0 Gb/s type: SSD serial: <filter> rev: 2.25 scheme: MBR
  Message: No optical or floppy data found.
Partition:
  ID-1: / size: 156.85 GiB used: 61.87 GiB (39.4%) fs: ext4 dev: /dev/sda1
    label: rootMX21 uuid: e4926c09-849f-4b41-a3e3-ac235a7798c4
Swap:
  ID-1: swap-1 type: partition size: 7.25 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sda2 label: swapMX uuid: 896c30f7-9e85-435a-a766-25c44ef764a9
Unmounted:
  Message: No unmounted partitions found.
USB:
  Hub-1: 1-0:1 info: Full speed or root hub ports: 6 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-2: 2-0:1 info: Full speed or root hub ports: 2 rev: 1.1
    speed: 12 Mb/s chip-ID: 1d6b:0001 class-ID: 0900
  Hub-3: 3-0:1 info: Full speed or root hub ports: 6 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Hub-4: 4-0:1 info: Full speed or root hub ports: 2 rev: 1.1
    speed: 12 Mb/s chip-ID: 1d6b:0001 class-ID: 0900
  Hub-5: 5-0:1 info: Full speed or root hub ports: 2 rev: 1.1
    speed: 12 Mb/s chip-ID: 1d6b:0001 class-ID: 0900
  Device-1: 5-1:2 info: Broadcom BCM5880 Secure Applications Processor with
    fingerprint swipe sensor
    type: N/A driver: N/A interfaces: 1 rev: 1.1 speed: 12 Mb/s power: 100mA
    chip-ID: 0a5c:5801 class-ID: fe00 serial: <filter>
  Hub-6: 6-0:1 info: Full speed or root hub ports: 2 rev: 1.1
    speed: 12 Mb/s chip-ID: 1d6b:0001 class-ID: 0900
  Device-1: 6-1:2 info: Cambridge Silicon Radio Bluetooth Dongle (HCI mode)
    type: Bluetooth driver: btusb interfaces: 2 rev: 2.0 speed: 12 Mb/s
    chip-ID: 0a12:0001 class-ID: e001
  Hub-7: 7-0:1 info: Full speed or root hub ports: 2 rev: 1.1
    speed: 12 Mb/s chip-ID: 1d6b:0001 class-ID: 0900
  Device-1: 7-2:2
    info: N-Trig Duosense Transparent Electromagnetic Digitizer type: Mouse
    driver: ntrig,usbhid interfaces: 3 rev: 1.1 speed: 12 Mb/s power: 500mA
    chip-ID: 1b96:0001 class-ID: 0301
  Hub-8: 8-0:1 info: Full speed or root hub ports: 2 rev: 1.1
    speed: 12 Mb/s chip-ID: 1d6b:0001 class-ID: 0900
Sensors:
  System Temperatures: cpu: 53.0 C mobo: N/A sodimm: SODIMM C
  Fan Speeds (RPM): cpu: 0
Info:
  Processes: 184 Uptime: 1h 19m wakeups: 2 Init: SysVinit v: 2.96 runlevel: 5
  default: 5 Compilers: gcc: 10.2.1 alt: 10 Packages: note: see --pkg
  apt: 2099 Shell: Bash v: 5.1.4 running-in: xfce4-terminal pinxi: 3.3.15-1
harry@biker:~
$       

Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.

Linux Registered User # 475019
How to Search for AntiX solutions to your problems

[Forum Admin rokytnji]

Yeah Brian. This was hardware battle. On boot removable which is usb boot. No bootable device found. Double checked on another box. On MX work bench dvd. Got to wallpaper on boot but then screen froze. Only thing that took for starters and I installed and ran.

https://forum.puppylinux.com/viewtopic.php?t=6220

which fit on cd. DVD reader was aLSO BEING PICKY.

Being stubborn. Went to the dollar store and bought me a dvdr + disc since none were on my shelf. Finally got antiX 21 full to load up on that dvd and boot.
I hurried through the install afeared hardware issues again. Hence the large swap partition shown in inxi9 and conky. I already fixed that though. It takes a bit for me to throw this in the dumpster.
Wife bought it brand new with Windows Vista on it. Ran like molasses.

I am happy camper now on this unit. Makes a good spare. Posting this on the Dell as Acer needs a rest from that big update/upgrade I did asfter initial install..

$ inxi -M
Machine:
  Type: Desktop System: Dell product: OptiPlex 755 v: N/A
    serial: <superuser required>
  Mobo: Dell model: 0GM819 serial: <superuser required> BIOS: Dell v: A11
    date: 08/04/2008

I played it safe and said No to using package maintainers version when asked in the root account. Kept the defaults for now. Did not feel like starting over after a all day session.

• This reply was modified 7 months ago by rokytnji.

Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.

Linux Registered User # 475019
How to Search for AntiX solutions to your problems

During the past few days, Conky has seemed as if it’s crashing. I think this problem is the result of doing updates. (Several days ago, I did a massive updating session using Syaptic, and this problem never happened before that.) Conky used to start up and be displayed on the screen at initial boot time, but now it doesn’t get shown at all without direct intervention.

When I use the menu to start it (Menu click/ Desktop/ Conky on/off), the 1st click seemingly does nothing, then the 2nd click puts Conky up on the desktop. My suspicion, is that Conky is actually running, but not visible on the desktop – and the 1st click turns it off. Then, the 2nd click turns it on and it becomes visible – but, for less than a minute. After which, it vanishes again.

Here’s the output of “inxi -Fxxxrz”:
——————–

System:
  Kernel: 4.9.0-264-antix.1-amd64-smp arch: x86_64 bits: 64 compiler: gcc
    v: 8.3.0 Desktop: IceWM v: 3.0.0 vt: 7 dm: SLiM v: 1.3.6
    Distro: antiX-19.4_x64-full Grup Yorum 20 May 2021
    base: Debian GNU/Linux 10 (buster)
Machine:
  Type: Portable System: Dell product: Latitude E6400 v: N/A
    serial: <superuser required> Chassis: type: 8 serial: <superuser required>
  Mobo: Dell model: 0U692R serial: <superuser required> BIOS: Dell v: A34
    date: 06/04/2013
Battery:
  ID-1: BAT0 charge: 76.4 Wh (102.0%) condition: 74.9/76.4 Wh (98.1%)
    volts: 12.2 min: 11.1 model: Panasonic DELL FU44196 type: Li-ion
    serial: <filter> status: full
CPU:
  Info: dual core model: Intel Core2 Duo P8600 bits: 64 type: MCP
    smt: <unsupported> arch: Penryn Yorkfield rev: A cache: L1: 128 KiB
    L2: 3 MiB
  Speed (MHz): avg: 1200 high: 1600 min/max: 800/2401 boost: enabled cores:
    1: 1600 2: 800 bogomips: 9576
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx
Graphics:
  Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Dell
    driver: i915 v: kernel arch: Gen5 ports: active: LVDS-1
    empty: DP-1, DP-2, DP-3, HDMI-A-1, HDMI-A-2, VGA-1 bus-ID: 00:02.0
    chip-ID: 8086:2a42 class-ID: 0300
  Display: x11 server: X.Org v: 1.20.4 driver: X: loaded: intel gpu: i915
    display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1280x800 s-dpi: 96 s-size: 338x211mm (13.31x8.31")
    s-diag: 398mm (15.69")
  Monitor-1: LVDS-1 mapped: LVDS1 model: Seiko Epson 0x5441 res: 1280x800
    hz: 60 dpi: 107 size: 303x190mm (11.93x7.48") diag: 358mm (14.1")
    modes: 1280x800
  OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express v: 2.1 Mesa 18.3.6
    direct render: Yes
Audio:
  Device-1: Intel 82801I HD Audio vendor: Dell driver: snd_hda_intel
    v: kernel bus-ID: 00:1b.0 chip-ID: 8086:293e class-ID: 0403
  Sound Server-1: ALSA v: k4.9.0-264-antix.1-amd64-smp running: yes
Network:
  Device-1: Intel 82567LM Gigabit Network vendor: Dell driver: e1000e
    v: 3.2.6-k port: efe0 bus-ID: 00:19.0 chip-ID: 8086:10f5 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel WiFi Link 5100 driver: iwlwifi v: kernel bus-ID: 0c:00.0
    chip-ID: 8086:4232 class-ID: 0280
  IF: wlan0 state: down mac: <filter>
RAID:
  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
    v: 3.0 port: 6ea0 bus-ID: 00:1f.2 chip-ID: 8086:282a rev: N/A
    class-ID: 0104
Drives:
  Local Storage: total: 1.14 TiB used: 288.89 GiB (24.8%)
  ID-1: /dev/sda vendor: Toshiba model: MK2561GSYN size: 232.89 GiB
    speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: 0C scheme: MBR
  ID-2: /dev/sdb type: USB vendor: Western Digital
    model: WD My Passport 0748 size: 931.48 GiB type: N/A serial: <filter>
    rev: 1019 scheme: MBR
Partition:
  ID-1: / size: 28.71 GiB used: 7.43 GiB (25.9%) fs: ext4 dev: /dev/sda5
Swap:
  ID-1: swap-1 type: partition size: 9.77 GiB used: 30.9 MiB (0.3%)
    priority: -1 dev: /dev/sda3
Sensors:
  System Temperatures: cpu: 41.0 C mobo: N/A sodimm: SODIMM C
  Fan Speeds (RPM): cpu: 3013
Repos:
  Packages: apt: 2141
  Active apt repos in: /etc/apt/sources.list.d/antix.list
    1: deb http://mirrors.rit.edu/mxlinux/mx-packages/antix/buster/ buster main nonfree nosystemd
  Active apt repos in: /etc/apt/sources.list.d/buster-backports.list
    1: deb http://deb.debian.org/debian/ buster-backports non-free contrib main
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://ftp.us.debian.org/debian/ buster-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://ftp.us.debian.org/debian/ buster main contrib non-free
    2: deb http://security.debian.org/ buster/updates main contrib non-free
  No active apt repos in: /etc/apt/sources.list.d/onion.list
  No active apt repos in: /etc/apt/sources.list.d/various.list
Info:
  Processes: 210 Uptime: 13h 13m wakeups: 11 Memory: 3.82 GiB
  used: 1.52 GiB (40.0%) Init: SysVinit v: 2.93 runlevel: 5 default: 5
  Compilers: gcc: 8.3.0 alt: 8 Shell: Bash v: 5.0.3 running-in: roxterm
  inxi: 3.3.19

• This topic was modified 6 months, 4 weeks ago by anticapitalista. Reason: added solved

[Member ModdIt]

Original Poster seems unable to give a reasl answer 😉
Anyway Reducing swappiness to 10 is not the smartest idea for good overall desktop performance.
Upgrading memory or installing a modern SSD or NVME is whenever possible far better.
Even a modern SSD with IDE adapter is faster on long writes than an anchient HDD. Means faster swapping.

An Excerpt: From a very sensible discussion at https://askubuntu.com/questions/184217/why-most-people-recommend-to-reduce-swappiness-to-10-20
Reading the whole thread is recommended.

Because most believe that swapping = bad and that if you don’t reduce swappiness, the system will swap when it really doesn’t need to. Neither of those are really true. People associate swapping with times where their system is getting bogged down – however, it’s mostly swapping because the system is getting bogged down, not the other way around. When the system swaps, it will have already factored the performance cost in to its decision to swap, and decided that not doing so would have a greater overall penalty in system performance or stability.

Overall the default settings result in good overall performance and stability. I’d recommend leaving it at the default. There are further avenues for Linux to improve its memory management to solve some edge cases, but by and large the swappiness control isn’t a good workaround – adjust it in one direction and you may fix one issue and create other issues. If at all possible, simply installing more physical RAM (and leaving swappiness alone) eclipses all other remedies.

How Linux uses RAM

Any RAM that isn’t being used by applications may be used as “cache”. Cache is important for a fast, smooth running system, speeding up both reads and writes to disk.

If your applications increase their memory use to the point they are using almost all your RAM, your cache will shrink and on average disk operations will slow down as a result. It’s not enough to have just tens of megabytes, or less, for cache nowadays.

If applications increase their memory use even further – assuming you have no swap space – you will not only have no space for cache but you will eventually run out of memory and your system will have to kill running processes. Killing processes is worse than a slow down as it gives you an unstable, unpredictable system.

How Linux uses swap

To combat both of these problems, your system can re-allocate some seldom-used application memory to the swap space on your disk, freeing RAM. The additional RAM can prevent processes dying due to running out of memory, and can reclaim a little cache so disk operations can operate more smoothly.

This re-allocation isn’t done according to a definite cutoff though. You don’t reach a certain percentage of allocation after which Linux starts swapping. It has a “fuzzy” algorithm. It takes a lot of things into account, which can best be described by “how much pressure is there for memory allocation”. If there is a lot of “pressure” to allocate new memory, then it will increase the chances some will be swapped to make more room. If there is less “pressure” then it will decrease these chances.

Your system has a “swappiness” setting which helps you tweak how this “pressure” is calculated. It’s often falsely represented as a “percentage of RAM” but it’s not, it’s just a value that is used as part of the formula. Values around 40 to 60 are the recommended sane values, 60 being default nowadays.

Letting your system swap when it has to is overall a very good thing, even if you have a lot of RAM. Letting your system swap if it needs to gives you peace of mind that if you ever run into a low memory situation even temporarily (while running a short process that uses a lot of memory), your system has a second chance at keeping everything running. If you go so far as to disable swapping completely, then you risk processes being killed due to not being able to allocate memory.

What is happening when the system is bogged down and swapping heavily?

Swapping is a slow and costly operation, so the system avoids it unless it calculates that the trade-off in cache performance will make up for it overall, or if it’s necessary to avoid killing processes.

A lot of the time people will look at their system that is thrashing the disk heavily and using a lot of swap space and blame swapping for it. That’s the wrong approach to take. If swapping ever reaches this extreme, it means that swapping is your system’s attempt to deal with low memory problems, not the cause of the problem, and that without swapping your running process will just randomly die.

What about desktop systems? Don’t they require a different approach?

Users of a desktop system do indeed expect the system to “feel responsive” in response to user-initiated actions such as opening an application, which is the type of action that can sometimes trigger a swap due to the increase in memory required.

One way some people try to tweak this is to reduce the swappiness parameter which can increase the system’s tolerance to applications using up memory and running low on cache space.

However, this is just shifting goalposts. The first application may now load without a swap operation, but it will leave less slack for the next application that loads. The same swapping may just occur later, when you next open an application instead. In the meantime, the system performance is lower overall due to the reduced cache size. Thus, any benefit from the reduced swappiness setting may be hard to measure, reducing swapping delay at some times but causing other slow performance at other times. Reducing swappiness a little may be justified if you know what you’re doing, but reducing it to as low as 10 can leave the system tolerant to very low cache sizes and leave the system more liable to have to swap at short notice.

Disabling swap completely should be avoided as you lose the added protection against out-of-memory conditions which can cause processes to crash or be killed.

The most effective remedy by far is to install more RAM if you can afford it.

[Moderator christophe]

Regarding the antiX version of zram, it comes with a nicely preconfigured default of 20-25% of RAM being used (according to my experience). And that also appears to be an estimate based on the compression percentage it expects to get, so the amount of RAM used is much less than the size of the zram swap file reported.
So, in antiX (I cannot speak to how any other distro handles it), it is preconfigured nicely. Once the 2 commands are run (as above), just reboot — and it’s active.

confirmed antiX frugaler, since 2019

[Moderator Brian Masinick]

Frequently swapping creates a heavily I/O bound workload, which makes the slowest resources also be the system’s resource constraint. Personally I don’t favor that approach; to everyone I suppose you can do whatever you want; be prepared for what happens though.

--
Brian Masinick

[Moderator Brian Masinick]

I don’t know what some story has to say about swap.

On one of my 64 bit UNIX workstations some ~25 years ago I was able to run virtually everything directly from memory and I set a kernel flag to NEVER swap. While that doesn’t work for all possible workloads it certainly worked on my workstation, which ALSO had a powerful UNIX server providing disk space and the heavy hitting networking and compute power so that the workstation could edit files, access server resources and the network.

Worked great and I was never close to consuming all of memory or running out of resources.

Your use cases may be different but in my opinion swapping out processes is RARELY a good idea.

--
Brian Masinick

[Forum Admin anticapitalista]

Do you have some arguments for using swappiness 10 on machines with 700mb or lower RAM? If yes, I’ll be very happy to read it.

No. I asked you for evidence that swappiness of 60 is better. You haven’t provided any yet.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member Mad Daimond]

anticapitalista wrote:

Indeed, it is debatable and depends on many factors and not just on the ‘general principle’ of ‘The more RAM you have – the less swappiness value you can set’.

Do you have some arguments for using swappiness 10 on machines with 700mb or lower RAM? If yes, I’ll be very happy to read it.

BobC wrote:

One suggestion, if you don’t want freezes, don’t ask more of the PC than it has to give.

Actually, I have posted the solution to my problem in the first post. But Zram is the thing to try, thank your for that!

[Member oops]

Mad Daimond wrote:

I have an old laptop Dell Latitude 110l with Intel Pentium M 1.6 Ghz, 768mb RAM. And I had a problem with Antix-19 – when there was a little amount of free RAM the system was near in full freeze with HDD LED always turns on. The problem of this was a wrong setting for the swap file – when free RAM was near the end, the system aggressively tries to free it and of top of it it starts to write the swap file at the same time. To resolve this issue you need to do:
sudo nano /etc/sysctl.conf
find the line:
vm.swappiness = 10
and change it to:
vm.swappiness = 60

This makes your system to start using the SWAP much earlier (when there will be near 50% of free RAM) and when the free RAM will be at near end this is not overkill your system, like it was with swappiness 10 (which is recommends for the PC’s with near 16+GB RAM, by the way). Hope this will helps to someone.

In you case, maybe you can leave vm.swappiness = 10 (instead default 60)
and set:
vm.vfs_cache_pressure = 50 instead 100 by default


vm.swappiness = 10
vm.vfs_cache_pressure = 50


[Forum Admin anticapitalista]

The swappiness is somewhat debatable thing, and its often recommends to test the comfortable swappiness value by yourself to you system. But the general principle is “The more RAM you have – the less swappiness value you can set” and vice versa.

Indeed, it is debatable and depends on many factors and not just on the ‘general principle’ of ‘The more RAM you have – the less swappiness value you can set’.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member Mad Daimond]

BobC wrote:

Investigate zram.

Minimize what programs you are running. Do you have the antix-goodies package installed?

Yes, I have AntiX-goodies installed. As far as I understand, to use the zram, you need to install and configure it. Instead of it can I just use:
sudo zram start

with AntiX-goddies installed?

anticapitalista wrote:

Got a source for this recommendation? Preferably one that refers to using a modern 4/5 series kernel.
Thanks.

The swappiness is somewhat debatable thing, and its often recommends to test the comfortable swappiness value by yourself to you system. But the general principle is “The more RAM you have – the less swappiness value you can set” and vice versa.

• This reply was modified 7 months ago by Mad Daimond.

[Forum Admin anticapitalista]

… like it was with swappiness 10 (which is recommends for the PC’s with near 16+GB RAM, by the way). Hope this will helps to someone.

Got a source for this recommendation? Preferably one that refers to using a modern 4/5 series kernel.
Thanks.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

I have an old laptop Dell Latitude 110l with Intel Pentium M 1.6 Ghz, 768mb RAM. And I had a problem with Antix-19 – when there was a little amount of free RAM the system was near in full freeze with HDD LED always turns on. The problem of this was a wrong setting for the swap file – when free RAM was near the end, the system aggressively tries to free it and of top of it it starts to write the swap file at the same time. To resolve this issue you need to do:
sudo nano /etc/sysctl.conf
find the line:
vm.swappiness = 10
and change it to:
vm.swappiness = 60

This makes your system to start using the SWAP much earlier (when there will be near 50% of free RAM) and when the free RAM will be at near end this is not overkill your system, like it was with swappiness 10 (which is recommends for the PC’s with near 16+GB RAM, by the way). Hope this will helps to someone.

[Moderator Brian Masinick]

Speaking of the Liquorix kernel, here are the choices this particular kernel makes and the trade-offs associated with these choices; the result is an extremely responsive INTERACTIVE kernel:

* PDS Process Scheduler: Fair process scheduler for gaming, multimedia, and real-time loads.
* High Resolution Scheduling: 1000hz tick rate for precise low jitter task scheduling.
* Preemptible tree-based hierarchical RCU: RCU implementation for real-time systems.
* Hard Kernel Preemption: Most aggressive kernel preemption before requiring real-time patches. Guarantees responsive system under high intensity mixed workload scenarios.
* Budget Fair Queue: Proper disk scheduler optimized for desktop usage, high throughput / low latency.
* TCP BBR2 Congestion Control: Fast congestion control, maximizes throughput, guaranteeing higher speeds than Cubic.
* Compressed Swap: Swap storage is compressed with LZ4 using zswap
* Multigenerational LRU: Alternative LRU algorithm that performs better under high memory pressure and uptimes
* Binary Builds For Popular Debian Distros: Binary builds are produced for Debian Stable, Testing, and Unstable. Ubuntu builds are available on the Liquorix PPA same day within hours of Debian releases going up.
* Distribution Kernel Drop-in Replacement: Proper distribution style configuration supporting broadest selection of hardware.
* Paravirtualization options enabled to reduce overhead under virtualization.
* Minimal Debugging: Minimum number of debug options enabled to increase kernel throughput.

--
Brian Masinick