Any chance you’d consider adding a CLI switch or change the default logic to have --replotting-thread-pool-size run with the same priority as --plotting-thread-pool-size does? Something like --replotting-thread-priority could be used but that name may be confusing as its does not have the same logic change as --plotting-thread-priority does.
The use case is now that the app performance is so good at determining optimal default settings, it still requires custom thread settings as to not slow down the farmer once sectors expire on a completed drive and there is still plotting to be done on others.
With the current default settings, when a drive finishes plotting and starts working on expired sectors, its working on those sectors at half the threads that are used for plotting. That is slowing down overall plotting on other drives that have sectors to be finished.
Arguably, the CLI is being used more by farms that are using dedicated machines to farm as fast as possible vs Space Acres being used on less dedicated hardware.
A possible logic option could also be to use the more aggressive replotting thread priority until the sum of all NotPlotted sectors stated on the farmer are zero.
