Dear all, Recenly, I have installed the gLuster 3.2.2 source and do much IO performance on gLuster by tuning the cache-size and cache-timeout. And I found the cache-size doesn't work for multi bricks whick is strange and stuck me. For example, volume info: Volume Name: strip-vol Type: Stripe Status: Started Number of Bricks: 2 Transport-type: tcp Bricks: Brick1: cloud04:/web-data01/data02 //multi bricks Brick2: cloud04:/web-data01/data03 Options Reconfigured: performance.cache-refresh-timeout: 60 performance.cache-size: 1024000000 test scripts: for((i=0;i<3;i++)); do dd if=f20M of=/dev/zero bs=1M; sleep 2;done test results: First test: Description: distributed volume with multi bricks [root at cloud04 testfs]# for((i=0;i<3;i++)); do dd if=f20M of=/dev/zero bs=1M; sleep 2;done 20+0 records in 20+0 records out 20971520 bytes (21 MB) copied, 0.107977 seconds, 89 MB/s 20+0 records in 20+0 records out 20971520 bytes (21 MB) copied, 0.108642 seconds, 85 MB/s 20+0 records in 20+0 records out 20971520 bytes (21 MB) copied, 0.10802 seconds, 90 MB/s
