• 2 Posts
  • 29 Comments
Joined 3 years ago
cake
Cake day: February 1st, 2023

help-circle



  • Ideally, we wouldn’t build infinite compute, just as much as we are actually using, and using it efficiently allows you to build less. We would still need datacenters even without LLMs, but they wouldn’t need to be so gargantuan, because even the worst, inefficient, nodejs-based, intern-written server you could ever encounter, would be heaps more efficient (or at least less demanding) than any LLM. This is true even from an economical point of view, or any practical point of view, not just environmental.

    To quote Tannenbaum: “You know you have the right computer when you are always using 99% of it. If you are using 100%, you are being limited by the machine. If you are using 98% you have bought more than you need”. If datacenters were always running at 40%, we would build bigger ones.









  • edinbruh@feddit.ittoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    1 month ago

    That is not a good method for testing. Maybe the filesystem still requires new files to be smaller than free space. Or maybe the file could be not really compressible, for example, you won’t be able to compress random data. You also won’t compress already compressed data, like videos.

    You could write a real text file of some kB and then check the compression ratio with something like “compsize”.

    The mount command mounts the disk with the options you give to it but only once. Now, because you don’t want to manually run mount everytime you use your disk, you must set it up so it is always mounted with the options you want. Udisks2 is one of the tools for that.

    edit: apparently compsize is btrfs only. You can use “du” with and without --apparent-size and check the differenze




  • edinbruh@feddit.ittoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 month ago

    So, first of all, there is no gui for this, that I’m aware of, so you will have to do it from terminal. Second, on f2fs, compression works that you don’t enable compression for a folder, instead you mount the drive with compression enabled, and new files will be compressed automatically.

    So what you need is to set up your disk to be mounted with compression. There are many paths you can follow here. If you want your drive to be (almost) permanently connected, the easiest way is to use “/etc/fstab”. If you want to use it as a regular SD card, mounting and ejecting it from your file explorer etcetera, then you should go here and learn how to have udisks2 mount your device with compression, which should be what your desktop environment uses to mount drives. I suggest you set that up for your specific device, and not for all f2fs devices. Good luck.

    You can look up other useful f2fs options on the arch wiki. I suggest you add all those options that reduces writes to your disk and improve durability (like lazytime).

    You should use zstd as compression algorithm, and because this is a slow and small drive, you can crank up the level of compression.

    If you manage to pull this off, the next time you install a (bigger and faster) drive on your pc, you can try to look into zfs.


  • edinbruh@feddit.ittoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    5
    ·
    1 month ago

    If it’s a flash memory (sd card, usb stick, ssd, etc), you could try f2fs, it’s very light, and it supports compression and is meant specifically for that kind of devices (well, more for ssds).

    But judging your experience from your comments, I suggest you don’t delve into niche filesystems until you have more experience with Linux, especially for something like 128MB. I especially suggest you avoid zfs for now.