bladebit-cuda-v3.1.0-rc1-ubuntu-x86-64 second plot much slower than first one.

[Peter82kr]

Im using rc1 version because disk 16 option is hundrets times slower on 3.1 stable release.

After linux reboot im getting 53-57 minute plot on rtx 4070 + 32 gb ram + 5800x3d + kingston kc3000 nvme ssd.

Second plot is always slower and im getting 71 minutes or more. Dont know how to solve it, Its just +/- 500MB/s write to nvme instead of gigabytes as it was during first plot.

Its not fault of ssd temperature. Drive has 50 celsius degrees.

Ram is not filled its about 9 gigs used and swap is 0% used during plotting.

ALWAYS after system reboot im getting faster plots speeds and ALWAYS second plot is slow.

Im plotting on mxlinux 23.1 ahs x64

This is my command line for running bladebit:
./bladebit_cuda -f XXXXXXXXXXXXXXX -c XXXXXXXXX --count 2 --compress 3 cudaplot --disk-16 -t1 /mnt/658276fa-83f1-4463-a4e8-2ab90cb6133a/chiatemp/ /mnt/local_share/

Destination is samba share on my farmer machine wchich is latest debian. Writing to temp on destination is always stable about 115MB/s

Main difference between first and second plot is write speed to nvme ssd.

I am not experienced linux user so i will be grateful for simple language in posts below.

EDIT:

Checked again latest stable bladebit version 3.1 . Currently works. On earlier releases of mxlinux haved mentioned problems.
Currently 3.1 stable works BUT STILL first plot afer rebot is faster than second plot after reboot. First plot 37.9 minutes and second 41.32 minutes. Currently results are more acceptable for me and i will not complain. BUT if we know what is changed with pc during reboot we can speed up all plots no mater there is reboot or no reboot.