[–] [S] 1 point 5 days ago

Sorry, I cannot follow you.

There is no reason at all, to not have physical swap when using ZRAM. My physical swap just has a lower priority and is never used, when using ZRAM.

You claim that there is no performance difference, once you have >= 8 GB of RAM. I would assume it is much relevant what kind of usage is thrown at ZSWAP/ZRAM instead of the size. Perhaps you could elaborate, why, in your opinion one will not observe a difference in performance and why this limit would be exactly 8GB? I also use ZRAM on my 8GB machines, with a physical swap partition as backup and physical swap is never touched.

OOM killer is IMHO independent of ZSWAP/ZRAM, because swap space has an upper limit anyway, and a functioning OOM killer is IMHO preferable to a crashed system. I was just surprised, that the OOM killer did not work for me, when using ZSWAP, because IMHO it should have killed the browser in my example.

Finally, why do you claim that ZRAM performs better on low-memory devices, because I do not see a reason that it should, or that such a generic answer makes sense.

Please understand my intention here: I want to understand WHY you make these statements and what is the technical reasoning behind them.

  • source
  • parent
  • context
  • [–] [S] 1 point 5 days ago (2 children)

    Sorry, my English is not good enough.

    ZSWAP basically crashed. The computer had no stutters, it stopped working at all. It did not really feel slower with ZSWAP vs. ZRAM.

    I used the same computer with exactly the same desktop/browser configuration, so it should be a 'fair' comparison between ZSWAP/ZRAM.

    I also have to add, I am using ZRAM on high memory devices, too, w/o any trouble. ZRAM should IMHO even perform better, when you have more memory, because the RAM disk can be bigger and hold more data.

  • source
  • parent
  • context
  • [–] [S] 1 point 5 days ago

    Thank you for the warning!

    I am not sure I used 'freezing' in the correct way, my machine has a full (I guess) out of memory crash. Since the physical swap runs full, I assume i/o should be ok. Sometimes I also install games from GOG on this machine, which is heavy read/write i/o, so again, I guess that i/o is not the problem here.

  • source
  • parent
  • context
  • [–] [S] 2 points 5 days ago (2 children)

    Thanks a lot for sharing. I am happy, it is not just me.

    Fedora uses ZRAM w/o swap by default since a few years AFAIK. ZRAM is to the best of my knowledge also heavily used in Android phones w/o swap and of course Chromebooks w/o swap.

    For me, swap is never used when ZRAM is activated, I will probably not setup a partition for new installations of Debian.

    I still do not get, why it seems that people like Chris Down are so strong in their recommendation for ZSWAP. Chris seems to work at META and probably sees primary server workloads. But I would expect a developer of his caliber to be able to understand and formulate, where ZRAM beats ZSWAP and the other way around. Even in his article above, he is a little bit more nuanced concerning his recommendations. My personal takeaway for now is, to use ZRAM on desktops unless I really need/want hibernation.

  • source
  • parent
  • context
  •  

    I am a happy ZRAM user for several years now. Basically it makes my 4GB netbook totally usable running Gnome and a Browser with a lot of open tabs.

    After reading Debunking zswap and zram myths last week, I thought to give ZSWAP a trial, since the machine had a 3 GB swap partition anyway.

    I disabled ZRAM, and enabled ZSWAP and configured it to use the defaults with ZSTD.

    I would have expected, that my machine would perform as good as with ZRAM, perhaps a little bit slower because of accessing SWAP instead of just using the RAM.

    Surprisingly, my machine froze using ZSWAP after opening at most half the amount of tabs in my browser that I would open when using ZRAM. Was the first freeze on this machine I can remember, after I made the switch to ZRAM.

    I increased the zswap.max_pool_percent from its default of 20 percent to 50 percent, which improved the situation a little bit, but still the machine froze again.

    I saw the the physical swap was being utilized.

    I reverted back to ZRAM, where I configure by default the size to be double the amount of RAM, something like 8 GB (!), again with ZSTD. I could open an insane amount of tabs again, I saw that nothing was swapped to the physical swap, everything was in the RAM disk. No trouble, no freezing.

    My question is, why do I observe this? Should not ZSWAP with 50 percent of RAM and a physical SWAP partition outperform ZRAM, at least concerning the number of open tabs in the browser? (I could understand a performance loss because of swapping to the SSD.) Why does the out of memory systemd service not trigger properly with ZSWAP?

    Using Debian 13 on an Intel Celeron, in case that should be relevant.

    Update:

    • I understand, that ZRAM is just a compressed RAM disk and that the 8GB I configure is the size of the compressed data on it, not the actual size it takes in memory
    • I understand, that ZSWAP is a caching layer in front of regular swap, integrated into the memory manager subsystem of Linux

    According to my understanding, this still does not explain, why ZRAM outperforms ZSWAP. The physical RAM consumption of ZRAM with a lot of open tabs is roughly 2GB. ZSWAP should have had roughly 1.9 GB of RAM for compressed pages ) + 2.9 GB of physical swap. If we assume a compression factor of 3 this sould be roughly 1 GB of additional swap compared to ZRAM, which still performs worse. Again, in both cases ZSTD was used.

    Update 2: When I write 'freeze', I mean full out of memory crash when using ZSWAP. The machine 'freezes' fully, inclusive mouse cursor and nothing happens, even if I leave it alone a few minutes. Sorry, English is my 2nd language.

    [–] 4 points 1 year ago

    At the moment, I am trying to clear ascension 20.

    My chance of winning the game up to ascension 5 is > 50%.

    IMHO StS gives the player bad habits in the lower difficulties (and the difficult spike when reaching the heart is not that great).

    Some tips stolen from better players than me:

    • You really have to play optimal and think about every card to minimize life loss (This could also mean taking a hit early and kill off an enemy faster vs. blocking an early hit and taking massive damage later.)
    • The bosses especially can be seen as problem to solve. Look ahead, do you have the right card(s) in the deck to solve the problem?
    • The first hall is mostly about about up front damage, in the second you will need some area of effect damage etc.
    • Before adding a card to your deck, answer the following questions:
      • How high is the chance I can even play this card? (Example: You have 3 energy and a card costs 2 Energy. If you have another 2 Energy card, you know increase your chance of a dead draw, because you can not play both if they appear in the same hand)
      • Does this card has any synergy with the cards I already have in my deck or with any artifacts?
      • Does this card solve a problem (e.g. boss or enemy) I have? IMHO all the generic advice is not wrong (like having as little cards as is possible), but the point about playing the higher ascensions is really more seeing 'the whole' instead of focusing on one aspect. For example, if you have Corruption in a bottle and Dark Embrace, all of a sudden you want to have as many skills a possible... OTOH, if you have two Dropkicks, you want everything which destroys cards to have an endless Dropkick-Engine as soon as possible.
    • Take care of immediate problems you know you will face (like the boss of the current hall), instead of speculating on card combinations which might or might not show up in the future. (Exception to the speculation rule: Iron Clad has Limit Break, and it is total reasonable to expect to find some strength boost as an Iron Clad, so LimitBreak is usually the one card which I never think about picking up)

    tldr: Picking your strategy and adding/removing of cards must be seen in the context of artifacts, energy and the bosses you will see. Optimize for your next known problem, instead of betting in cards to become available. You can have 1-2 cards for special situations or as speculation, but adding for example another attack card if you already have enough of attack, simply doesn't solve a problem or makes your deck stronger.

  • source
  •  

    According to a book I am reading, diet science currently agrees that there is one way to loose weight: A calorie deficit.

    For example, if I need 2000 kcal a day and eat only 1500 kcal a day, I will loose some weight over the next weeks/months.

    To my understanding, calories here are totally interchangeable, if we are only concerned with loosing weight (and ignore nutrients etc).

    Calories are basically measured by burning food and measuring how much energy was set free.

    My question is: Why and how does it work so good and why are calories interchangeable?

    In more detail: Why can we translate the burning of calories with fire to processing the calories in food with our digestion system so perfect? Why is there no difference (concerning weight loss), if I eat 1500 calories as pure sugar or eat them as pure protein (where I would assume the body needs more energy to break down the protein)?

     

    Question is in the title: What is the supposed workflow for vanilla Gnome for keyboard users?

    Is there any video/design documents which explain, how the workflow is supposed to be?

    Assume, I have a full screen web browser on workspace 1. Now I want to have a terminal... I hit the super-key, type terminal, hit enter ... and then I have a terminal which does not start maximized on workspace 1, so I can either maximize the terminal and switch between the applications, arrange them side by side... or I can navigate to workspace 2, start the terminal there (the terminal will not start maximized again on an empty workspace 2) ... and switch between the two workspaces (AFAIK there are no hotkeys specified by default to navigate directly to a workspace)...

    What I simply do not understand: Does the vanilla Gnome workflow expect you to use mouse and keyboard? Like hit super, use mouse to go to next workspace, type terminal, click to maximize terminal (or use super-up)?

    It just seems like a lot of work/clicks/keys to achieve something simple. And to my understanding Gnome expects you to use basically every application with a full screen window anyway, so why does it not open a new application on the next free workspace full screen by default?

     

    When using TMUX, it is easy to create a script, which opens TMUX, configures the screens/panes of TMUX and open/run programs.

    I like this a lot.

    My baseline would be something like, when I login, some applications are executed and their windows automatically placed on a virtual desktop.

    For example:

    • Open Firefox and put it on virtual desktop 1
    • Open Terminal in fullscreen and put it on virtual desktop 2
    • Open VSCode and put it on virtual desktop 3

    Something like that is possible with sway, in the environment I am working, sway is not able to run XWayland applications w/o crashing.

    Is there any way to have this functionality on Gnome, Mate, Xfce?

    Even better would be something to open several windows and arrange them automatically for different work tasks/projects I am working on. Any ideas?

    Edit: Solved! Thanks for the input. Auto Move Windows extension for Gnome solves my problem.

    view more: next ›