[New File Placement Limit?]

Balancing can be very slow, as we use a background IO Priority for the task. This is to avoid causing any sort of performance issues with the system. For lower end systems, that's a very good idea. But for higher end systems, it may be beneficial to use more resources. But we want to default to lower to prevent issues.

 

The Advanced settings for DrivePool can help:

http://wiki.covecube.com/StableBit_DrivePool_2.x_Advanced_Settings

FileBalance_BackgroundIO

FileDuplication_BackgroundIO

 

Set these values to "False", and it may help with the speeds.

 

Cheers for the info, brought the speeds back up again. 33MB/s to 100MB/s

[New File Placement Limit?]

Also, if you're using the "Ordered Placement" option in the SSD Optimizer, then there are a couple of settings you need to tweak to get this to behavior correctly:

• UNCHECK "File placement rules respect real-time file placement limits set by the balancing plug-ins."
• CHECK "Balancing plug-ins respect file placement rules."
• UNCHECK "Unless the drive is being emptied."

But could you clarify which balancers are enabled, which order, and the specific settings?

 

The above fixes the problem. I was only using the SSD Optimizer with ordered placement left at defaults. I used the rules in the file placement tab inside balancing to set which disks were used for duplicated folders and unduplicated ones. This allows me to run from a single SSD feeder and then balance and duplicate overnight. I did notice a problem with the balancing being very slow but I'll post about that in a new thread after I've done some more testing.

 

Cheers.

[New File Placement Limit?]

Also, to be clear here, if you're using the SSD Optimizer, then you don't want ot use the Ordered File Placement balancer on the same pool, as it causes issue. Instead, use the "Ordered File Placement" section in the SSD Optimizer.

 

Hi all, merry christmas!

 

Is there anyway to use the SSD Optimizer with the rules set in the file balancer tab. ie after the files are present on the SSD have duplicated files and non duplicated files get to written to different disk sets in the pool. At the moment the non duplicated files get moved to a random disk that might be a drive set for duplicated files. I see you can set which order of disks to use in the SSD Optimiser plugin but i'm not really after filling the disks up in a set order.

 

If I disable the SSD Optimiser the files always get moved to the correct disks.

[Archive Optimizer functionality]

Try moving the automatic balancing trigger slider to 100%. There might be an issue with the logic not working on the 1GB data limit you have set. Worth a try.