Leaderboard

Hello, Christopher (Drashna). Yes, in my scenario, the combination of immediate balancing and "not more often than every X hours" doesn't work very well. In my scenario, because there are instances where I frequently write several hundred gigabytes of files, it's necessary to start immediate balancing once the SSD's capacity reaches a certain level of occupancy. Otherwise, it would either become impossible to write to Drivepool due to insufficient free space on the SSD, or it would require bypassing the SSD and writing directly to slower HDDs. Therefore, immediate balancing without using "not more often than every X hours" is essential in my environment. Moreover, it would be great to have a feature to start balancing at a specific time every day, disregarding the threshold set in "Automatic balancing - Triggers." If, during my sleeping hours, Drivepool could automatically start balancing to maintain free space for SSD Optimizer, it would reduce the balancing time occurring during waking hours. This would minimize the performance degradation of Drivepool during waking hours, allowing for more efficient operation of Drivepool.