Current role assignment may not always optimise the best parameters. For example, if you have fewer stateless class processes in your cluster than proxies configured, you will get fewer proxies than you asked for. You may prefer FoundationDB to run proxies on other processes e.g. storage servers. But this needs some thought, as then you may get unpredictable performance as some storage servers will have more CPU load than others.
At the very least I think FoundationDB should warn to the user undesirable configurations of process sharing (particularly log and storage sharing) or if recruited counts are less than desired counts.
Current role assignment may not always optimise the best parameters. For example, if you have fewer stateless class processes in your cluster than proxies configured, you will get fewer proxies than you asked for. You may prefer FoundationDB to run proxies on other processes e.g. storage servers. But this needs some thought, as then you may get unpredictable performance as some storage servers will have more CPU load than others.
At the very least I think FoundationDB should warn to the user undesirable configurations of process sharing (particularly log and storage sharing) or if recruited counts are less than desired counts.