Vadim Fint

If u have >=512GB ram it would be better do not use DMA/SYNC but rely on big dirty system cache ```diff --git a/src/platform/unix/FileStream_Unix.cpp b/src/platform/unix/FileStream_Unix.cpp index 0e7ce41..7268138 100644 --- a/src/platform/unix/FileStream_Unix.cpp +++...

75 plots/day on 2690v2! 

> seeing the plot write straight to HDD taking increasingly longer as the plotting continue this is expected for rotational media (i.e. hdd's) - constant read/write speed varies. Usually os/nas/whatever...

I'm `fallocate`-ing 101GiB, because avg plot size is around 101.35GiB and smallest I have seen is 101.25GiB (10k+ plots). It could be possible to allocate more here (e.g. 102GiB), but...

-n 999999 works for me

> It appears that the larger the -n the longer it takes to complete each plot. On my system -n 600 gives me 7 min 15 seconds but -n 800...

Yes. I am sure bladebit slows down after 50+ plots done. After restarting bladebit only speed recovers immidiately.

I guess you can remove/add background target by cron... :)

Regarding to random read: bcachefs seems to do something with background_target device (each bio?). In iostat that looks like same amount of seeks as it would be in direct reads...

you can run qtile with kde in a different and much more accurate form. disable plasma-kwin_x11 user service ``` systemctl --user disable plasma-kwin_x11.service ``` 1. set KDE_FULL_SESSION=true (without that big...