(_____(_____________(#)~~~~~~

  • 15 Posts
  • 554 Comments
Joined 3 years ago
cake
Cake day: April 11th, 2022

help-circle




  • I already stopped visiting 3 websites I used to frequent because I suddenly got redirected to Anubis and was told to enable JS. All my browsers have JS disabled by default and are configured to never keep any local storage/cookies out of principle. I won’t change that just to get to a website that is mostly static HTML. Even on the occasion where I bite the bullet it takes between 5 - 30 seconds to complete the PoW challenge on my main machine. I hope this trash doesn’t get popular. I really doubt that this makes much difference to more sophisticated crawlers that run on enterprise hardware.







  • FuckBigTech347toTechnologyVulkan on risc-v
    link
    fedilink
    arrow-up
    5
    ·
    1 month ago

    Affordable Desktop Hardware. Right now all RISC-V hardware that’s not just a naked SBC costs a small fortune. Once there are mass produced pre-built RISC-V boxes for the average person then RISC-V will become more widespread.







  • This reads like it was written by some LLM.

    Enable journaling only if needed:
    tune2fs -O has_journal /dev/sdX

    Don’t ever disable journaling if you value your data.

    Disk Scheduler Optimization
    Change the I/O scheduler for SSDs:
    echo noop > /sys/block/sda/queue/scheduler
    For HDDs:
    echo cfq > /sys/block/sda/queue/scheduler

    Neither of these schedulers exist anymore unless you’re running a really ancient Kernel. The “modern” equivalents are none and bfq. Also this doesn’t even touch on the many tunables that bfq brings.

    Also changing them like they suggest isn’t permanent. You’re supposed to set them via udev rules or some init script.

    SSD Optimization Enable TRIM:
    fstrim -v /
    Optimize mount settings:
    mount -o discard,defaults /dev/sdX /mnt

    None of this changes any settings like they imply.

    Optimized PostgreSQL shared_buffers and work_mem.
    Switched to SSDs, improving query times by 60%.

    No shit. Who would’ve thought that throwing more/better hardware at stuff will make things faster.

    EDIT: More bullshit that I noticed:

    Use ulimit to prevent resource exhaustion:
    ulimit -n 100000

    Again this doesn’t permanently change the maximum number of open files. This only raises the limit for the user who runs that command. What you’re actually supposed to do is edit /etc/security/limits.conf and then relog the affected user(s) (or reboot) to apply the new limits.

    Use compressed swap with zswap or zram:
    modprobe zram echo 1 > /sys/block/zram0/reset

    This doesn’t even make any sense.