i already made the filesys with this bs-size, and will see how its going, but looks great.

Which mount-options would you choose if you’re in my position?

i tried with max_write/read=131072 but filesys wasn’t mounted, so i decided to mount with 4096 is this to low?

At this moment 20GB are transfered and the speed is still at 2-3MB/s (its transfered over internet and i set the transfer-limit to 5mb/s)

sounds not bad, but 52hours for transfer, argh…
do i have to make another mklessfs after changing the bs??

At this time this is not the problem, because its only testing, but when the system is online, there should be a way to increase the size of the bs without destroying any data.

What type of data are you storing on lessfs? For example tar or vtl files?
Lessfs compression should be equal to that of commercial vendors.

The number of threads only effect the performance and should be 30% less then the number of cores in the system with a minimum of 1.

Use a 32k block size for small files.
Use a 64k block size for most workloads.
Use a 128k block size for max performance.

Make sure that the _BS values are tuned.
For max performance compile with –with-sha3 and put the FILEBLOCK and BLOCKUSAGE databases each on there own raid one disk set. The faster these disks are the better. BLOCKDATA can be on raid5/6.

You should increase the numbers you see above. These settings are usable for testing small datasets. For production you need at least 2MB or ram for every 1 million records stored.

Mark.

The transfer to the lessfs folder starts really fast, but after ~10GB onle 180kb/s are written.

What can i do??