Good day, We have automation that uses the "bssplit" function to get a wide variety of IO patterns, I have noticed that in 2.13 (compiled with no-shared-mem). The bsssplit only takes the first variable, meaning: bssplit=1k/50:128k/50 will yield a 100% 1k workload. This is the workload: [global] random_generator=tausworthe64 direct=1 loops=1 ioengine=libaio iodepth=16 group_reporting filename=/dev/disk/by-uuid/27602b49-4a18-4dca-a896-e2fc86746015 [workload] rw=randread bssplit=1k/50:128k/50 I tried to work around this using block range but when using a large number of targets, ~150, the memory consumption is around 150GB. Thank you for your help! Ryan -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
